Moving coding agent memory off-machine: from Dropbox CONTEXT.md to MCP shared memory
Asly97 · reddit · 2026-09-17
A developer splitting time 50/50 between desktop and laptop documents his journey fixing agent amnesia: Dropbox-synced CONTEXT.md was stale or ignored; self-hosted Mem0 on Postgres turned him into a database maintainer. What stuck: putting memory outside both machines via Vilix AI's MCP shared memory — semantic retrieval, last-write-wins corrections, both clients on one account. Limitations: per-client setup, approvals don't carry over, and unsaved sessions are lost. His advice: stop syncing files, put memory where both clients can read it.
Related event: Developers seek persistent memory for coding agents across devices(2 posts)→
More from coding & agent
- Tencent unveils Hyra 2.0, a research agent that builds reusable scientific tools — TencentHunyuan · 2026-11-02
- What broke when I ran a leaderless agent swarm with no orchestrator — 7 failure modes and fixes — LostHumanity67 · 2026-11-02
- Forced yes/no prompts push GPT and Claude to 95%+ confidence on Goldbach's unproved halt test — Nir777 · 2026-11-02
- Automation took over my daily work — so why am I still sitting in the office for 8 hours? — Am1rSori · 2026-11-02
- General Reasoning explains how to train agent swarms with RL and latency pressure — rosstaylor90 · 2026-11-02
- "Coding isn't the bottleneck anymore — usage windows are," says founder Kyle Gawley — kylegawley · 2026-11-02