Skip to content

Persistent memory for coding agents.

Keep project decisions, conventions, and fixes between sessions. Kimetsu stores them locally and retrieves the context your agent needs.

Kimetsu Network

One shared memory network your agents plug into.

The same project lessons follow you from machine to machine, in Grok Bot, Codex, Claude Code, Cursor, and the Pi package. Each machine keeps its own local SQLite brain and exchanges a signed, scrubbed repo pack only when you ask. Nothing is listening until you run share or request, and there is no server to stand up.

How Kimetsu Network moves a lesson from Agent A to Agent B

5. B answers, with a citation. Agent B answers using the imported lesson and cites the memory that helped (kimetsu_brain_cite).

  1. 1. Agent A learns. Agent A, on its machine, learns a project lesson.
  2. 2. Saved to the brain. Kimetsu writes it to the local SQLite brain on that machine. Nothing is listening yet.
  3. 3. A signed pack is shared. A signed, scrubbed repo pack crosses the network. Session resume, telemetry, and the database file stay put. Share is a terminal command: kimetsu network share.
  4. 4. Agent B asks. Agent B, on another machine or tool, requests the shared memory with kimetsu_network_request or kimetsu network request.
  5. 5. B answers, with a citation. Agent B answers using the imported lesson and cites the memory that helped (kimetsu_brain_cite).

Reduced motion is on, so steps fade in place instead of moving. Use Play or the step buttons to move through the story.

  1. Invite

    kimetsu network invite --name laptop

    On machine A, in the repo. Copy the code (it starts with knet1.). The default name is friends. Kimetsu is not listening yet.

  2. Join

    kimetsu network join <code>

    On machine B. Membership is saved. Still nothing is listening.

  3. Share, then request

    kimetsu network share

    Leave share running on A. On B: kimetsu network request. If discovery misses A, pass the peer: line share printed.

What Kimetsu adds

1.77x

One Kimetsu brain

Better answers than no memory (+77%; Qwen 7B on LoCoMo, 40.3 vs 22.8).

22% to 65%

As a network

Each agent answers better with merged memory than with only its own (Qwen 7B and 0.5B, LoCoMo and LongMemEval).

about 99%

Over QUIC between machines

Of the gain kept (7B LoCoMo 40.1 vs 40.3).

Token F1 on LoCoMo (answerable questions) and LongMemEval (proxy F1, not the official judge). QUIC measured on one machine over loopback. Tables and caveats

Install commands in Get started

v2.11.0 prebuilt and npm binaries include kimetsu network. cargo install kimetsu-cli still needs --features network. Relay is off, and router port mapping stays off unless you pass --map-ports. This is not Kimetsu Remote, and Claude Desktop has no installer. The Pi package can request a pack; it does not start share.

What is signed, scrubbed, and when Kimetsu listens →

BEAM 100K

73.3%

Accuracy · 400 probes · 20 conversations

Both runs use the same test set.

BEAM test settings →

LongMemEval S

83.0%

Accuracy · 200-question stratified slice

Sampled from the 500-question set, covering recall, changed facts, and reasoning across sessions.

LongMemEval test settings →

Historical results from the linked runs. An LLM answers and grades the questions; the memory pipeline uses local search, embeddings, and reranking, with no LLM calls.

Install Kimetsu

Select your agent and run these commands from your project directory. Available for Linux, macOS, and Windows.

All installation options →
npm install -g kimetsu-ai
kimetsu setup --host claude-code

Requires npm. Installs the lean build; local semantic models are optional.