Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y [email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add io.github.rxthlessbeats-agent-cowork-memory -- npx -y agent-cowork-memory@0.3.2รันในเทอร์มินัล
{ "mcpServers": { "io.github.rxthlessbeats-agent-cowork-memory": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
█████╗ ██████╗███╗ ███╗
██╔══██╗██╔════╝████╗ ████║
███████║██║ ██╔████╔██║
██╔══██║██║ ██║╚██╔╝██║
██║ ██║╚██████╗██║ ╚═╝ ██║
╚═╝ ╚═╝ ╚═════╝╚═╝ ╚═╝
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.
Shared memory and delegation for Codex, Cursor, Claude Code, and OpenCode.
Verified by benchmark: on 38 held-out tasks, a new chat continuing with ACM finished 223 of 228 runs, against 130 with a pasted summary.
Codex · 
Claude Code · 
Cursor · 
OpenCode
More demos on the ACM official site
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.
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.
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).
What it evaluates
What we tested
Result
npm run bench # offline checks, free
npm run bench:live # the live benchmark; spends your Codex quota
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).
--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.
Shared memory and delegation for Codex, Cursor, Claude Code, and OpenCode.
{ "mcpServers": { "io.github.rxthlessbeats-agent-cowork-memory": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Agent Cowork Memory ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-10 Shared memory and delegation for Codex, Cursor, Claude Code, and OpenCode.