kage://releases

# Releases

Current package status, what changed for users, and the canonical links. Kage ships through npm as `@kage-core/kage-graph-mcp`.

Current package

## v2.2.1

2.2.1latest on npm + the official MCP registry — June 12, 2026
238tests passing on every release
0dependencies, accounts, or API keys required

    npx -y @kage-core/kage-graph-mcp install

User-impact highlights

## What changed for users

v2.2 — memory that follows you Personal memory in `~/.kage/memory` with `kage sync` over your own git remote; conflicts resolve newest-wins with both versions preserved. Plus the `kage merge-packet` git driver, a signal gate that keeps junk out of auto-capture, and `kage audit-claude-mem` — a read-only truth report over an existing claude-mem store.
v2.1 — the session loop closes itself Auto-distill captures sessions the agent forgot to save (drafts, reviewed by you); `kage resume` opens each session with a "previously…" digest; `kage repair` fixes broken packets and indexes in one command; `<private>…</private>` spans are never stored.
v2.0 — verified knowledge + receipts The Truth Report (`kage scan`), the per-repo value ledger behind `kage gains`, change-time stale-catch in `kage pr check`, tree-sitter AST extraction for five more languages, and the Gains-first viewer.
Receipts got real Every packet records what it cost to learn (`discovery_tokens`); recall receipts report measured replay value, never estimates dressed up as facts.
Memory at the moment of reading A PreToolUse hook injects verified packets the instant the agent reads a file they cite — checked against the code first, never blocking.
The viewer went live Packets and value events stream into the viewer in real time over SSE while the agent works.
npm package GitHub releases Changelog Repository
Release channels

## Where to look

npm is the source of installable package truth. GitHub releases are human-readable milestones. CHANGELOG.md records package-level changes across versions.