Local-first memory kernel live on npm

Repo memory for coding agents.

Codex learns it today. Claude Code recalls it tomorrow. Kage turns durable discoveries into source-backed repo memory that travels with your code.

ask your agent ambient after restart
Install and set up Kage for this repo.
Open Viewer
86passing tests
13agent setup targets
0external databases
98%smaller context in same-task A/B
MCPCodex, Claude Code, Cursor, more
The hive memory loop

One agent discovers. Every future agent starts informed.

Kage does not save chat exhaust. It captures resolved, reusable, source-backed knowledge: why something changed, how to run it, where it lives, and what can break next.

Agent discovers

Codex finds a workflow, bug fix, convention, command, package pattern, or code path.

Kage writes

The agent writes repo-local packets with paths, evidence, quality, freshness, and source refs.

Git reviews

Repo memory is visible as normal JSON changes. Secrets are blocked before write.

Git carries it

Packets live in the repo as plain JSON. No hidden vendor silo required.

Agents recall

Claude Code and other MCP agents retrieve compact context before they act.

Graphs with provenance

Separate code truth from learned memory.

The code graph is rebuilt from source. The memory graph is built from repo-local packets. That separation keeps Kage useful instead of turning sessions into junk nodes.

kage graph --live evidence locked
code graph symbols/calls repo hive local-first kernel promotion org/global review packets JSON in git evidence paths/source refs recall agent context
files -> symbols -> callsSource-derived graph facts for routes, imports, tests, packages, and flow.
packets -> entities -> edgesRepo memory becomes typed graph facts with provenance, content freshness, and quality.
BM25 + graph retrievalRecall blends BM25 lexical ranking with graph, path, type, tag, intent, quality, freshness, and feedback signals.
estimated savingsToken savings are estimated from compact context today; production telemetry is not overclaimed.
Real Codex + Claude Code handoff Codex recalls Kage memory in one terminal session. Claude Code recalls the same packet from the same repo.
Actual hosted viewer Live Kage repo graph, search, memory/code views, and metrics.
Two agents. One repo memory.

Ask the agent to install it. Then work normally.

Kage installs a CLI, an MCP server, and a repo policy. After restart, agents should recall, query, learn, and write memory without the user saying "use Kage" every time.

Codex

npm install -g @kage-core/kage-graph-mcp
kage setup codex --project . --write
kage init --project .
kage setup verify-agent --agent codex --project .

Claude Code

npm install -g @kage-core/kage-graph-mcp
kage setup claude-code --project . --write
kage init --project .
kage setup verify-agent --agent claude-code --project .
Trust model

Repo memory is immediate. Org/global memory is reviewed.

Repo-local memory should feel automatic: agents learn, write packets, and future agents recall them. The human gate starts when memory leaves the repo boundary.

repoAgents write approved repo packets directly under `.agent_memory/packets/`.
scannedSecrets, tokens, credentials, private URLs, and PII are blocked before capture.
visibleRepo memory is git-visible, diffable, and reviewable in the same flow as code.
promoteOrg/global upload, public candidates, registry packs, and CDN bundles require explicit review.
Ships now

Local-first, npm-installed, no external database.

The launch package is intentionally sharp: repo memory and source graph for agents, with local org/global artifacts available without automatic publication.

CLI + MCP

`kage` and `kage-graph-mcp` ship from npm for Codex, Claude Code, and MCP clients.

Git-native memory

Repo packets are plain JSON under the repo, diffable like any other code artifact.

Code graph

Source-derived files, symbols, imports, calls, routes, tests, and package scripts.

Refresh + PR checks

Rebuild graphs, mark stale memory, summarize branches, and block content drift before merge without post-push refresh loops.

Viewer

Terminal-style console for graph inspection, packet inspection, and metrics exploration. Open the hosted viewer shell.

Honest boundary

No hosted SaaS claim. No automatic public publishing. No marketplace auto-install.