Releases

The v4 era.

Install from npm: npm install -g @kage-core/kage-graph-mcp. The store format is plain OKF markdown in git, and the local sqlite schema is versioned with ordered migrations — upgrades never eat your memory.

Current

v4.0.0 — collaborative repository memory, measured end-to-end

One proxy, every agent

Anthropic, OpenAI-compatible, and Gemini wires behind one background proxy — injection, reversible compression, and the same fail-open honesty gates on all three. Audit mode is the default: measurement only, bytes untouched.

Reversible history digestion

Opt-in: old tool outputs digest to deterministic summaries with exact originals retrievable. Measured on real bodies: −93.33% session request bytes. Single-body compression honestly measures ~0% and is reported as such.

Derivability-aware capture

Admission boosts what code cannot say (rationale, gotchas, run recipes) and routes restatements of cited code to review — the class the store audit measured at ~0 uses.

The team value report

kage report team: recalls served, stale withheld, the live injection gate, composition, dark areas, review health. Measured or labelled-estimate, never fabricated.

Team workspace (optional)

Tenant-isolated PostgreSQL workspace with review authority: approved-only sync, raw prompts never leave the machine, self-approval blocked, idempotent replays, append-only audit — each invariant a passing test against a real database.

Local portal + viewer

kage open: review queue, receipts, system maps, and the team value panel; the zero-build viewer stays for quick local inspection. Suite: 1474/1474 backend, 109/109 portal.

Honest status: the technical readiness gates pass; no design-partner pilot has run yet and the GA report says so (and exits non-zero) rather than pretending otherwise.

History

How it got here

v3 — the verification layer

Deterministic claim verification against real code, OKF as the storage format, the trust benchmark, staleness withholding. The core thesis: memory an agent can trust.

v2 — the memory loop

Ambient capture and recall for Claude Code: hooks, distillation, the packet store, the first dashboard. Where "memory as plain files in git" started.

v1 — the graph MCP

The original knowledge-graph MCP server that gave the npm package its name.