---
title: "Claude Code memory shared with every coding agent | Keep"
description: "Give Claude Code, Codex, Cursor, OpenCode, and Pi shared project memory. Decisions, handoffs, and research carry between coding sessions."
canonical: "https://keep.md/uses/code"
language: "en"
---

# 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](https://app.keep.md/signup)

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.

**SessionStart:** 3 project notes found. D1 cost handoff, Search conventions, Launch decisions.

### Example questions

#### why are feed queries batched into one read?

**Keep tools:** search\_context, get\_note

Decision recorded Jul 23 in d1-cost-handoff: one read per page render, counts cached at the edge, after costs spiked 4x. Codex shipped it Jul 24 in PR #231. Open item: tag counts still read per render.

#### draft the launch post from what I saved about agent memory

**Keep tools:** search\_items, get\_item

Pulled three threads you saved this month and your positioning note from Jul 12. The draft leads with the shared-memory line and cites all three sources.

#### what do we know about competitor pricing?

**Keep tools:** search\_context

Four saved pages and one note. Every rival charges per seat. Your Jul 12 note argues flat pricing is the wedge, so the pricing page should lead with one number.

[Read the MCP docs](https://keep.md/docs/mcp)

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

**Project:** Keep. **Kind:** handoff. **State:** open.

-   \- \[x\] Batch feed queries into one read.
-   \- \[x\] Cache counts at the edge.
-   \- \[/\] Tag counts: Claude picked this up on fix/tag-counts.

**Attached sources:** Cost investigation, PR #231.

#### Recent activity

-   Claude Code picked up the next task in v14, now.
-   Codex wrote the session handoff in v13, yesterday.
-   Ian recorded the decision in v12, 2 days ago.

[Read the Notes docs](https://keep.md/docs/notes)

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 decisions**Record the tradeoff and the reason once. Agents can find it before changing the same part of the system later.](https://keep.md/docs/notes)[**Session handoffs**Carry completed work, failed approaches, and the next task across agents and days.](https://keep.md/docs/session-hooks)[**Repository references**Save useful repositories with their README and connect them to the project that needs them.](https://keep.md/docs/github)[**Attributed changes**See whether a human or an agent changed a note, compare revisions, and restore an earlier version.](https://keep.md/docs/agents#review-agent-changes)

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 free](https://app.keep.md/signup)

[Read the MCP docs](https://keep.md/docs/mcp)