ₙMEMORY · LOCAL MEMORY FOR CODING AGENTS

Memory

That knows
when not to answer.

Every session starts cold.
Yours shouldn’t.

  1. 01

    Capture

    Provenance enters with the memory.

  2. 02

    Recall

    Freshness travels with the answer.

  3. 03

    Boundary

    The caller stays smart. The store stays honest.

  4. 04

    Custody

    One file you own. Nothing phones home.

The trust boundary

A memory is evidence.
Never authority.

Loading the maned wolf…

The sentinel — it guides recall.
It never decides what is true.

  1. 01

    Grounded

    A real capsule matched. Source, anchor, freshness, and relevance come with it.

  2. 02

    Missing evidence

    Matches existed, but every one was excluded — superseded, falsified, or stale.

  3. 03

    Abstain

    Nothing matched. No guess, no plausible filler, and no invented fourth answer.

The mechanism

Capture. Retrieve.
Ground or abstain.

Local-first nMEMORY architecture: a coding agent connects over MCP stdio to one Rust binary and one local SQLite file, with no sockets or telemetry
Local-first architecture
The three honest recall outcomes: grounded, missing evidence, or abstain
The one rule
Comparison between nMEMORY and a typical memory layer
Two philosophies

Local candidate · adoption is the final proof

Stop paying for
your agent’s amnesia.

nMEMORY on GitHub