Agent Cowork Memory MCP Server

Agent Cowork Memory (ACM)

 █████╗  ██████╗███╗   ███╗
██╔══██╗██╔════╝████╗ ████║
███████║██║     ██╔████╔██║
██╔══██║██║     ██║╚██╔╝██║
██║  ██║╚██████╗██║ ╚═╝ ██║
╚═╝  ╚═╝ ╚═════╝╚═╝     ╚═╝

Hit your Codex limit mid-task? Open Cursor, say "continue from Codex", and keep going. ACM gives Codex, Claude Code, Cursor, and OpenCode one shared memory, so you never paste context again, and any agent can put the others to work.

Verified by benchmark: with Codex on 38 held-out tasks, ACM finished 223 of 228 runs, against 130 with a pasted summary. Cursor and OpenCode performed similarly with ACM and summaries.

Codex  ·  Claude Code  ·  Cursor  ·  OpenCode

Demo

More demos on the ACM official site

Install

With Node 24 or newer:

npx agent-cowork-memory setup

Setup adds ACM to Cursor, and to Codex, Claude Code, and OpenCode when they are installed; Installed one later? Run setup again. Restart your agents, and ACM is available in every project.

Tested for real on Linux and WSL. macOS and Windows pass CI; real runs welcome.

Use

Memory Sharing

Open the same project in Codex and Cursor. To pick up a chat in the other agent, ask:

Use ACM to continue from Cursor.

Or, in Cursor:

Use ACM to continue from Codex.

Every agent can see every chat in the project. If there is more than one, the agent lists them (agent, time, thread, first message, and whether ACM started it for a delegated job) and asks you which one to continue. You can also name it:

Use ACM to continue the Codex chat about the trip.

Related work goes together in a thread: continuing a chat, or delegating from it, keeps the work on one thread, and a new chat can join one of the project's open threads. ACM keeps each thread's timeline as things happen (chats joining, jobs starting and finishing, notes added), so any agent can see where the work stands.

Ask your agent to remember a decision, and every agent in the project sees it. Notes stay true.

Delegate to other agents

Any agent can hand work to the others:

Tell codex to write plan.md, and claude to write packing.md.

Each agent gets a brief, joins the thread it was sent from, claims the files it edits so they don't collide, and reports back. Agents run in the background. With herdr installed, each one gets its own pane you can watch (herdr session attach acm). If you resumed a chat that's open in a herdr pane, work for that agent goes back to that chat, in its pane.

Benchmark

What it evaluates

• How much of earlier chats' context survives when a new chat continues the work.
• Each task is a small Python repo in two steps: earlier chats do step 1 and leave step 2's details in the chat.
• The details sit in one short or long chat, spread over two chats, changed later, corrected mid-chat, or against a README that still says the old thing.
• A run counts only if every hidden check passes, existing tests still pass, and no old or replaced value is implemented.

What we tested

• Codex (gpt-6-luna, medium effort), Cursor (Grok 4.7 High), and OpenCode (GLM-5.3-Flash), continuing the work five ways:
  • no ACM;
  • ACM ("Use ACM to continue from my last chat…");
  • the summary the earlier chat writes when asked;
  • a careful handoff note, including any Markdown files its turn wrote;
  • every earlier chat pasted in.
• Held-out tasks written before the runs, with the analysis fixed in advance. Pilot checks and earlier-chat guards determine which tasks count for each agent.
• Two independent histories, 3 runs per way per history; no ACM runs once per history.

npm run bench        # offline checks, free
npm run bench:live   # the live benchmark; spends your agent quota

MCP tools

ACM tells which chat it is in on its own; no tool needs a session or, from the project folder, a path (every tool takes an optional repo_path).

CLI

--home <dir> (or ACM_HOME) moves ACM's state folder from ~/.agent-cowork-memory. Run them with npx -y agent-cowork-memory <command>, or acm once it's installed globally.