How one developer is trying to keep Cursor, Claude Code, and Codex sharing the same context
Asleep-Pilot-4142 · reddit · 2026-07-29
The author describes a real pain point when switching between Cursor, Claude Code, and Codex: each agent loses the prior project context, stale hand-maintained docs quickly drift, and naïve state-dump scripts introduce too much noise. The eventual workaround is MEMMY, a shared memory hub built on memos that scans local chat histories, Cursor DB files, Claude JSON logs, and Codex rollouts, then exposes the same context to each agent through a small skill installed in their rules directory.
The post is still cautious: the main open question is whether the shared memory system will mix context across different projects. But it frames context continuity as the real problem for multi-agent workflows, not just prompting.
Related event: MindGraph: Persistent Graph Memory for Coding Agents(8 posts)→
More from coding & agent
- 'LLM code is sloppy' rebutted with real ffmpeg code: identical if/else branches in a top library — kingslyj · 2026-10-16
- Office-editing tool calls need file, worktree and unit: lessons from dsh-univer-office — FunDistribution6537 · 2026-10-16
- Architect MD workflow: Gemini one-shot outputs that beat Opus, via 5-lens plan critique — oikk01 · 2026-10-16
- Prove a coding agent actually ran the tests: check artifacts, not approvals — ComprehensiveShake76 · 2026-10-16
- Building an acceptance harness for AI spreadsheet edits: allowlists, recalc checks, idempotency — ukdicha-modakkk · 2026-10-16
- Agent actions need checks outside the model: NVIDIA demos lean on guardrails amid wave of real agent incidents — Creamy-And-Crowded · 2026-10-16