Keyoku Plugin Replaces OpenClaw's Static Heartbeat with Memory-Driven Autonomy

What Keyoku Changes

OpenClaw's current heartbeat system reads a static HEARTBEAT.md file on a schedule, responding with HEARTBEAT_OK. The agent has no connection between this heartbeat and its memory, lacking awareness of urgency, dropped tasks, or changes.

Keyoku replaces this by making the heartbeat check the agent's actual memory store every tick. It scans for items needing attention: stalled work, dropped commitments, conflicting information, quiet relationships, and patterns in your work.

How It Works

When the memory scan triggers an alert, the agent evaluates the full situation using all its knowledge, including a knowledge graph of people, projects, and their connections. Actions are then derived from memory, not from a pre-written checklist.

Instead of HEARTBEAT_OK, you might get a message like: "You mentioned you'd circle back on this last week. There are a couple things still open. Want me to help move them forward?"

Features and Architecture

• Three autonomy levels: observe (log only), suggest (surface to user, default), act (handle it directly).
• Behavioral logic: Backs off if ignored, won't nag about the same thing twice, treats urgent items differently from items that can wait.
• Enhanced memory layer: Deduplication, conflict detection, decay so stale information fades, knowledge graph that feeds into the heartbeat.
• Local execution: Runs a local Go engine with SQLite + HNSW on your machine.
• LLM integration: LLM calls go to your existing provider for extraction and analysis.

Getting Started

Install with: npx @keyoku/openclaw init

The stated goal is to make any agent autonomous, with OpenClaw as the starting point.