Context, memory, and continuity

Clawa keeps its living documents in the home. Before each agent turn, a bounded snapshot of CLAW.md, HUMAN.md, CLAWAS.md, CURIOUS.md, and TOOLS.md joins Pi’s native structured prompt. The snapshot refreshes after Pi compaction or optional Pi Codex continuity. Shared memory and chat notes are read separately when needed.

Notes, memory, and history

clawa_memory defaults to scope: "memory": Markdown shared by all Clawas under memory/. Use explicit scope: "notes" for stored chat and agent checkpoints under .pi/context/notes/. List, read, search, append, or write files. Update an existing page when it already owns the subject. Start at memory/index.md.

clawa_history reads Pi’s canonical JSONL sessions through the house catalog at .pi/context/chats/. Search prior windows, chats, and tools only when needed. It can also inspect committed revisions of shared memory. The catalog is not a second transcript database and a write does not automatically create a Git commit.

memory/legacy/ holds Markdown files containing exact JSON objects with id, ts, text, and original tags from the old SQLite memory database. Clawa imports existing rows on startup and leaves the database intact as a retired source. It never creates one when none existed. Move useful legacy material into maintained pages instead of editing the imports. A row larger than the shared file limit stops import visibly without truncating or changing the source database.

Continuity belongs to Pi

Plain Pi owns compaction, including /compact and overflow recovery. Optional Pi Codex owns its configured continuity. Clawa does not run a parallel rollover engine, disable Pi compaction, or configure context thresholds. Generic notes, history, new_context, and get_context_remaining are not Clawa tools. Use them only when your continuity extension provides them. Old Clawa notes and window archives are retained and remain accessible through the house tools.

Clawa launches and connects its residents itself. Neither resident coordination nor shared house memory requires Shepherdr or Codex. When optional Codex subagent sharing is enabled, Clawa uses Codex’s public identity API and its own resident sockets to connect fresh sessions before their first task. Codex still owns the notes, history, and continuity. Existing sessions are never rebound to a different family. See specialist Clawas for the compatibility boundaries.

Optional consolidation

/memory shows status. /memory remember freezes this conversation, starts a fresh one, and queues optional idle consolidation. /memory retry <jobId> retries a failed job. The memory bot uses a fresh private Pi session. It can edit only shared memory and the living-document owners, and leaves changes uncommitted. “Remembered” means that run finished successfully, not that a model’s judgment was independently verified.

Keep current work in the window, checkpoints in chat-local notes, reusable knowledge in shared memory or living documents, and older conversations in history. Do not turn transcripts into shared memory wholesale.