Memory for coding agents.
The session ends. The context stays.

Claude Code, Cursor, Codex, OpenCode, Hermes: every one of them starts the next session from zero unless you give it somewhere to keep what it learned. Supermemory is that place: decisions, conventions, debugging history and preferences, recalled when relevant and shared across every tool you use.

Files first, then memory

Start with AGENTS.md and CLAUDE.md. They are the right home for repo facts.

Durable, team-owned knowledge about a codebase belongs in Git: architecture, conventions, runbooks, the way this repo does things. It is reviewable in a pull request, deterministic, portable between agents, and easy to delete when stale. No memory system should replace that, and supermemory does not try to.

Memory starts where files stop.

What files can't hold

The knowledge	Why a file can't hold it
What the agent learned last session	Written after the session, not before it. Files only know what someone remembered to commit.
Your preferences as a developer	Personal, not project. They follow you across every repo, so they belong nowhere in one repo.
Context shared across tools	Claude Code, Cursor and Codex each keep their own. Nothing in Git carries a decision from one to the other.
What changed and when	A file is the latest truth. Memory keeps the current fact on top and the history underneath.

Supermemory sits alongside the files: the agent recalls what it learned in earlier sessions, saves what is worth keeping, and forgets what expired. Repo facts stay in the repo. Everything the repo can't say stays here.

Claude Code

A plugin, two commands, persistent memory across sessions and projects.

# Add the plugin marketplace
/plugin marketplace add supermemoryai/claude-supermemory

# Install the plugin
/plugin install supermemory

Set an API key from app.supermemory.ai in your shell profile, restart the terminal, and it runs on its own:

Reasoned recall.: Before each turn, Claude decides whether memory would help this message, and only searches when it is worth it.
Auto-capture.: Conversations and important tool usage are saved for later sessions. Nothing to remember to do.
Team memory.: Project knowledge is shared separately from personal memories, so a team works from the same decisions.
Explicit control.: /supermemory:index indexes the codebase's architecture; /supermemory:status shows where you stand.

Claude Code plugin in the docs

Every harness

The same memory, wherever the agent runs.

Harness	How it connects
Claude Code	The plugin above, with recall and capture built in
Cursor	The Cursor plugin, or the MCP server
Codex	The Codex integration
OpenCode	The OpenCode integration
Hermes	The Hermes integration
Your own agent	The MCP server or the API

Because it is one memory layer rather than one plugin per tool, a decision saved in Claude Code is there when you open Cursor. The agent changes; the context does not.

The supermemory MCP server

Self-hosted

Prefer everything on your own machine? The Claude Code plugin works against a local supermemory.

npx supermemory local

Point the project config at your local API and use the key printed on first boot. Same plugin, same memory, your hardware.

Self-hosting notes in the docs

Memory for coding agents.The session ends. The context stays.