Persistent engineering memory

Your coding agents should remember.

Persistent engineering memory for your coding agents: save a durable lesson once and recall it in every agent you connect.

  • Claude Code
  • Codex
  • Grok

Illustration

01 / Product

Knowledge that takes root.

Engineering lessons belong in a typed memory graph, with evidence, provenance, and Git context.

  • Durable engineering lessons such as decisions, proven fixes, conventions, and failed approaches.
  • Memory packs are designed for task-specific context instead of an unbounded history dump.
  • Memroot is designed to keep engineering knowledge independent of any one coding agent.
Example memoryDecision

Capture and redact sessions on the client, before upload.

Evidence
docs/decisions/0008-client-side-session-capture.md
Source
Claude Code session
Git
dev @ 0e33224
State
Current

The reset tax

Every new agent starts from zero.

WITHOUT MEMORY

Investigate. Rediscover. Repeat.

WITH MEMROOT

Carry the lesson forward.

02 / How it works

From session to signal.

  1. Connect your agents.

    Connect your coding agents through the Memroot MCP server. Each connection is authorized in the browser for one project.

  2. Keep the useful knowledge.

    Save structured engineering lessons with evidence and provenance.

  3. Start the next task ahead.

    Memory packs are designed to carry task-specific context, provenance, and staleness signals.

03 / Trust

Memory you can trust.

Useful enough to return. Careful enough to deserve a place in your workflow.

VERIFIED PRINCIPLE

Memories belong to the developer or project, not to one coding agent.

PRIVACY PRINCIPLE

Review and revoke each coding-agent connection from your console.

PRIVACY PRINCIPLE

Memroot stores structured engineering memories, not full coding-session transcripts.

VERIFIED PRINCIPLE

The memory graph records evidence, provenance, and explicit stale or superseded states.

04 / Pricing

Choose the plan that fits your work.

Free

Available

$0 / month

Limits

  • 1 project
  • 100 memory writes / month
  • 1,000 retrievals / month
  • 500 total memory writes
  • 1,000 total assertions
  • 30 data requests / minute

Account registration

Start free

Basic

Available

$9.99 / month

Limits

  • 5 projects
  • 1,000 memory writes / month
  • 10,000 retrievals / month
  • 5,000 total memory writes
  • 15,000 total assertions
  • 60 data requests / minute

Monthly subscription in USD. Review your plan and complete secure checkout after signing in.

Sign in to continue

Choose Basic

Max

Available

$49.99 / month

Limits

  • 100 projects
  • 15,000 memory writes / month
  • 200,000 retrievals / month
  • 75,000 total memory writes
  • 225,000 total assertions
  • 300 data requests / minute

Monthly subscription in USD. Review your plan and complete secure checkout after signing in.

Sign in to continue

Choose Max

Limits apply across your tenant. Monthly writes and retrievals reset each UTC calendar month. Total memory writes and total assertions are lifetime admissions; deleting memories does not restore them. An assertion is one atomic statement inside a memory; a memory can hold up to 8.

Works with

One memory. Any agent.

Memroot is designed around agent-neutral contracts.

Memory packs are designed to give agents relevant context on demand.

Memroot
  • Claude Code
  • Codex
  • Grok

More agents and adapters are on the way.

05 / Questions

The useful details.

What does Memroot remember?

Durable engineering lessons such as decisions, proven fixes, conventions, and failed approaches.

Does Memroot store full coding transcripts?

Memroot stores structured engineering memories, not full coding-session transcripts.

Which coding agents work with Memroot?

Claude Code, Codex and Grok are the featured examples. Memroot is designed around agent-neutral contracts, and more agents and adapters are on the way.

How does Memroot know when knowledge is stale?

The memory graph records evidence, provenance, and explicit stale or superseded states.

Who owns my engineering memory?

Memories belong to the developer or project, not to one coding agent.

Does this site collect card details?

This site does not collect card details. Paid subscriptions use secure checkout after you sign in.

How do I upgrade to a paid plan?

Choose Basic, Pro or Max, sign in, then confirm your monthly subscription through secure checkout. Manage your subscription from Billing in the console.

Continue the work

Let your next agent start where the last one stopped.

Create free account