Local-first memory for coding agents

Your agent
remembers.

Your agent remembers decisions, code context, and where the work stopped.

LOCAL SQLiteOPEN Apache-2.0READY MCP + CLI
MEMCODE / NATIVE AGENT
LOCAL / READY
memcode / native memoryready
MEMCODE / CURRENT SESSION SYNCED

Continue the CodeGraph work

$ memorix context --task "continue codegraph work"
CONTEXT PACKtask-shaped
01
Current codesrc/codegraph/context-pack.ts · current
02
DecisionMemory and CodeGraph stay separate
03
Next readsrc/codegraph/project-context.ts
ask, edit, test, resume
One coding session, with the context that should survive it.
NATIVE AGENTCode, context, continuity.
MEMORY LAYERCapture. Recall. Continue.

Works with your agent

One memory layer.
Everywhere you work.

Claude Code · Codex · Cursor · OpenCode · Gemini CLI · and moreAll integrations

From work to context

The work moves.
The signal follows.

Memorix turns a live coding session into a small, inspectable handoff for the next one.

Work

Your agent reads, edits, tests, and makes a decision.

Capture

The useful part becomes a source-labelled memory, not a transcript dump.

Continue

A new window starts with the right context and the right next read.

memcode / sessionsynced
MEMCODE / CURRENT SESSION SYNCED
01

Continue the CodeGraph work

Read. Edit. Test. Decide.

$ memorix context "continue codegraph work"
WORKING SETfresh
codesrc/codegraph/context-pack.ts
checksrelease gate / ready
decisionmemory and code stay source-backed
Memorix Dashboard showing project memory, sources, retention, and health
MEMORIX / CONTEXT PACKREADY
>

Finish the release

Context shaped around the next task.

01Decisionkeep the MCP startup gate fail-closed
02Verificationlegacy initialize and discover both pass
03Next readdocs / release checklist
WORKThe agent is in the loop.A real coding task is the source of the memory.

Dashboard

See what stays.
Keep control.

One local view for project memory, sources, retention, and health.

Explore the Dashboard
memorix / dashboardoverview
Memorix Dashboard overview showing memory sources, retention, and project status
Project memory, sources, retention, and health in one local control surface.

Product

Remember decisions.
Find the right context.

01

Continue the work

Small, task-shaped context for the next prompt, window, or agent.

Memory Autopilot
$ memorix context "finish the release"
selected: facts + verification + next steps
bounded / source-labelled
02

Understand the code

Source-backed files, symbols, and impact context. Memory Map is for memories; CodeGraph is for code.

CodeGraph context
entrysrc/embedding/provider.ts
impact3 related files
statecurrent
03

Keep the signal

Capture freely. Promote carefully. Let retention and review keep the working set useful.

Memory policy
observationssearchable
durable knowledgereviewed
old contextbounded

How it works

Capture once.
Continue anywhere.

  1. 01

    Work

    Your agent reads, edits, tests, and decides.

  2. 02

    Remember

    Useful context is captured and shaped.

  3. 03

    Continue

    The next task starts with the signal.

Built for the way agents work

MCP when it is there.
CLI when it is not.

02

CLI

A dependable command surface for every project and fallback path.

Read the API

Start with one command

Give your agent
a memory layer.

Install once. Keep working.

installmemorix

# install

$ npm install -g memorix

# connect

$ memorix setup --agent claude --global

Ready to remember.

FAQ

Simple outside.
Deliberate underneath.

Does it need an LLM key?

No. Local full-text retrieval works without one. Providers are optional.

Is it only for Claude Code?

No. Memorix works with the agents and MCP clients in the integration matrix.

Does it replay every old conversation?

No. Context is bounded and shaped around the current task.

Is Memory Map the same as CodeGraph?

No. Memory Map connects memories. CodeGraph connects source-backed code context.

Keep building

The next session starts
where the work left off.