Persistent identity
The orchestrator has a first-person IDENTITY.md, a USER.md, and standing context loaded through Claude Code hooks.
MindStone for Claude Code
MindStone for Claude Code (MS4CC) is the Claude Code substrate edition of MindStone Agent continuity. It gives a Claude Code orchestrator persistent identity, durable memory, checkpoint discipline, compaction handoff, and recall through Claude Code’s hook system.
For users who want MindStone Agent continuity today, MS4CC is one of the shipped paths.
The core idea is that memory is not one feature. LOG.md is audit, vector recall is not truth, .handoff.md is a rich continuity prompt for surviving compaction, identity is orientation, and structured memories are durable facts. MS4CC works because those layers cooperate instead of asking any one layer to pretend to be memory by itself.
Two MindStone terms matter here: a checkpoint is a governed synthesis step that promotes session experience into durable LOG, memory, transcript, and index state; a handoff is a detailed prompt for the next agent state, richer and more operational than a generic context summary.
What MS4CC provides
Section titled “What MS4CC provides”Structured memory
Important project facts, lessons, preferences, and decisions are promoted into durable Markdown memory files instead of being left only in chat logs.
Recall
Archived transcripts and memory files can be indexed and recalled so older context can return when it matters.
Checkpoint and handoff
Checkpoints synthesize durable memory; handoffs tell the next session what matters, what is unresolved, and how to resume after compaction or restart.
How it works
Section titled “How it works”MS4CC runs inside Claude Code’s hook and command model. There is no separate MindStone Agent server required for the core MS4CC continuity layer.
At a high level:
Session starts → identity, user context, LOG tail, and selected memory are injected
User sends a prompt → recall can surface relevant memory/transcript context
Checkpoint or compaction boundary approaches → LOG, memory proposals, transcript archive, vector backfill, and handoff preserve continuity
Next session starts → the orchestrator wakes with identity, user context, memory, and recent continuity restoredComponents
Section titled “Components”| Component | Purpose |
|---|---|
IDENTITY.md | First-person agent identity and working standards |
USER.md | Human/collaboration context |
LOG.md | Append-only continuity log for checkpoints, decisions, drift, and role spans |
memory/*.md | Structured memory files with frontmatter metadata |
transcripts/*.jsonl | Archived Claude Code session history |
.handoff.md | Rich compaction handoff for continuity after context reduction |
| hooks | Claude Code lifecycle integration for injection, recall, archive, and handoff |
/checkpoint | Checkpoint workflow for LOG/memory/archive/embed verification |