Keep

Give every coding agent the same project memory.

Keep carries decisions, handoffs, and research between Claude Code, Codex, Cursor, OpenCode, Pi, and the next tool you try. Each agent searches the same project library.

Start for free

01.

Start coding sessions with the latest project notes.

A session-start hook shows Claude Code, Codex, and Pi this project's notes before the first prompt. Cursor has a start-only preview. Every client can search the full library over MCP or the CLI.

Keep

MCPlive session
SessionStart3 project notes found

D1 cost handoff · Search conventions · Launch decisions

MCP serverRead the MCP docs

02.

One agent hands off. The next one continues.

Claude finishes a branch and writes down where things stand. Codex picks it up tomorrow and keeps going. Keep records who changed what, human or agent, with diffable history.

D1 cost handoff

open
Project
Keep
Kind
handoff
Sources
12

- [x] Batch feed queries into one read.

- [x] Cache counts at the edge.

- [ ] Tag counts still read per render.

- [/] Tag counts: Claude picked this up on fix/tag-counts.

Activity · 3 recent revisions

Claude Codepicked up the next taskv14 · now · +2 −1
Codexwrote the session handoffv13 · yesterday · +18 −0
IIanrecorded the decisionv12 · 2 days ago · +6 −2
Notes and historyRead the Notes docs

03.

Architecture decisions, handoffs, and the reasons behind them.

The library holds the context that usually disappears between a pull request, a debugging session, and the next agent prompt.

Architecture decisionsRecord the tradeoff and the reason once. Agents can find it before changing the same part of the system later.Session handoffsCarry completed work, failed approaches, and the next task across agents and days.Repository referencesSave useful repositories with their README and connect them to the project that needs them.Attributed changesSee whether a human or an agent changed a note, compare revisions, and restore an earlier version.

04.

Questions about memory for coding agents.

How do I give Claude Code a persistent memory?

Add the hosted Keep MCP server with one command, or install the CLI. A session-start hook shows Claude Code the latest notes for the project, and it can search the full library whenever a question comes up. The memory follows the project rather than one repo or one machine.

Does the same memory carry between Claude Code, Codex, Cursor, OpenCode, and Pi?

Yes. Every agent connects to the same library over MCP or the CLI. Claude Code, Codex, and Pi can save automatic end-of-session handoffs. Cursor uses a manual handoff prompt, while OpenCode installs an explicit /keep-handoff command.

How is Keep different from CLAUDE.md or auto memory?

Files like CLAUDE.md belong to one tool and one repo. Keep is a shared library with search by meaning, named revisions, and the source material behind each decision attached. Every agent you use reads and writes the same memory, across repos and machines.

Start the next coding session with the context intact.

Start for freeRead the MCP docs