Kage

What is Kage?

Kage is a framework for collaborative agent memory that is shared, code-grounded memory for developers and their coding agents. It captures a learning once—such as a bug cause, a decision, or a gotcha—so that the whole team plus every agent recalls it next time it is relevant.

How to use Kage?

Run the command npx -y @kage-core/kage-graph-mcp to try it in about 30 seconds. Memory is stored as git-tracked JSON that is reviewed in pull requests, and it works with any MCP client.

Key features of Kage

• Shared memory grounded in your actual code.
• Stored as git-tracked JSON reviewed in pull requests.
• Citations validated on write to maintain accuracy.
• Stale memory automatically withheld and flagged.
• Works with Claude Code, Codex, Cursor, and Windsurf.
• No vector database, API key, or service to run.

Use cases of Kage

• Capture a bug cause once so the whole team and agents avoid repeating it.
• Onboard new developers with an automatically recalled knowledge base.
• Keep coding agents consistent by giving them access to shared learned decisions.
• Review memory changes in pull requests like any other code change.

FAQ from Kage

Does Kage require any external services or API keys?

No. Kage does not need a vector database, API key, or any external service to run.

How is memory stored and reviewed?

Memory is stored as git-tracked JSON files, so changes are reviewed in pull requests like regular code changes.

What happens if the code that a memory references is deleted or refactored?

Stale memory—whose referenced code has been deleted or refactored—is withheld from recall and flagged for you, while citations are validated on write.

Which coding agents and MCP clients does Kage work with?

Kage works with Claude Code, Codex, Cursor, Windsurf, and any MCP client.