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
- Common ML pitfall: trusting external benchmarks over product-grounded evals — yunta_tsai · 2026-09-17
- TypeSafe's Jev ditches text generation for instant, calibrated numerical answers — and it plays Doom at 7 req/s — JnBrymn · 2026-09-17
- PostHog: Agent-Opened PRs Jumped From 20% to 70%, So What Do Engineers Do? — rseroter · 2026-09-17
- Non-developer builds GreekSoup, an open-source AI equity research desk, mostly by prompting Claude — Practical-Rise-1188 · 2026-09-17
- Google ships full agent lifecycle stack: context layers, self-heal, one-command deploy — blaizedsouza · 2026-09-17
- tldraw split its mascot favicon into three and serves one at random per page load — max__drake · 2026-09-17