kage-core/Kage

State an intent. Kage's orchestrator briefs a coding agent from your repo's own memory, runs it
in an isolated git worktree — a single run or a multi-wave goal — and **re-runs the checks
itself** rather than trusting the agent's report:
A real receipt from this repo's own run history. Every row is a command Kage ran or a fact
it inspected — never a claim the agent made about itself. kage merge only lands the code once
the claim holds, and ratifies what the agent learned, so the next brief, yours or a teammate's,
starts smarter.
That memory is the decisions behind your codebase, the runbook for a tricky deploy, the root
cause of a gnarly bug — captured as your agents work and checked against the actual code, so
what gets reused stays true. It's kept as plain Markdown files in your repo, conformant to the
Google Open Knowledge Format (OKF)
so there's no lock-in, and shared with your whole team through git. No account, no database,
no API key.
Website ·
Docs ·
Live viewer ·
npm ·
Book a demo
**Works with** Claude Code · Codex · Cursor · Windsurf · Gemini CLI · Cline · Goose ·
Roo Code · Kilo Code · OpenCode · Aider · Claude Desktop · Copilot · OpenClaw · Hermes · any MCP client
🌐 English · 简体中文 · 日本語 · 한국어 · Español · Português (Brasil) · Français · Deutsch · हिन्दी
---
Install
**One command, inside your repo, then restart your agent.** That's the whole setup.
It creates .agent_memory/, builds the code graph, writes the AGENTS.md / CLAUDE.md
policy that tells agents to use Kage, auto-detects and wires your agents, and configures
.gitignore + the packet merge driver. Requires Node.js 18+. No account, no API key.
**Or just ask your agent to set it up.** Paste this into Claude Code, Cursor, or any coding agent:
> Set up Kage (verified memory for coding agents, https://github.com/kage-core/Kage)
> in this repo: run npx -y @kage-core/kage-graph-mcp install, then tell me to restart you.
Other ways (plugin · per-agent · memory-only)
Delegate work (the orchestrator)
Every run works in its own git worktree. The checks that decide the verdict on the receipt
above — tests, diff size, citations — are commands **Kage** runs itself, never the agent's
self-report.
- **The app.** kage app --project starts (or reuses) the local daemon and opens the
same room, runs board, and memory view in a UI. From a checkout, npm start --prefix shell
runs it as a native window — a thin Electron shell with no HTML of its own, it just loads the
daemon's own page — and npm run dmg --prefix shell builds a macOS .dmg (arm64 only;
Windows/Linux packaging isn't built yet).
- **From your phone.** The daemon can also bind to your machine's LAN address, gated by a
pairing secret required on every request, reads included. Today that means setting
"lan": true in .agent_memory/config.json by hand — there's no --lan flag or app toggle
yet.
- **Add a project without a terminal.** kage projects add --agent claude registers
another repo the same way the app's "+" button does, then kage app --project opens it.
Desktop app
A thin native shell (macOS, arm64 only) over the same daemon the CLI runs — dock presence,
a global hotkey, native notifications. Download the latest .dmg from
GitHub releases (look for a
Kage- .dmg asset).
Unsigned builds show macOS's "unidentified developer" prompt on first launch —
right-click the app in Finder and choose **Open** once. Once installed, it checks for
updates on launch and every 4 hours and installs on restart; ad-hoc (unsigned) builds
can't self-install and notify you instead, linking back to the releases page.
Prefer the CLI? The one-line install works everywhere the app doesn't need to:
What is Kage
Kage is an orchestrator for coding agents, built on a memory layer. As your agent works, it captures what it learns
(decisions, bug fixes, conventions, how the code fits together) as