에이전트 강화
게시자의 자체 명령입니다. 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
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 stdio 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
이 레코드에는 필수 환경 변수가 등록되어 있지 않습니다.
Agent Cowork Memory은(는) stdio를 통해 로컬에서 실행됩니다.
마지막 확인: 2026-11-10. Shared memory and delegation for Codex, Cursor, Claude Code, and OpenCode.