The re-centralisation of AI Agents
A blog post, not a product—no code, no tool, no demo to evaluate.

Portable context via MCP and share links beats copy-pasting project specs into every new chat.
Developers and power users managing multiple AI agents and projects
Cursor Projects · Claude Projects · Mem.ai
This originally started as a CLI I built that kept pieces of context (Project A/B/C details, my writing style, preferred tech stacks, coding style, etc) in a SQLite database. I could instruct various agents to “use my `coremem` CLI to retrieve details about [project A] before we get started.” It solved a problem for me b/c I am continually bouncing around between different projects and chat agents, and having to re-explain myself every time became an exercise in either repeating myself or copy/pasting summaries I’d saved from previous sessions.
I decided to make this a little more robust and portable, so I turned that original CLI into a SaaS. Tl;dr: You can create a “mem”, which is a collection of 1 or more pieces of related context, and share that mem with any agent to quickly get them up to speed.
Right now I’ve got integrations in the form of revokable share links, a Chrome Plugin, Cursor Plugin, Cursor/VS Code extension, Claude Code plugin, ChatGPT/Claude/Gemini/et al via MCP. Since I mostly work from the CLI, I use the Claude Code plugin or create 5-min share links I can drop into a chat, but I’ve tried to make this useful to people who mainly work from a browser or an IDE.
I’ve been coding for 30+ years, and I vibed most of this. I was able to use CoreMem to help it built itself as I jumped between various coding agents, having them grab context then start a new task. I’m sure my architecture and engineering experience helped, but building this in a few weeks confirmed for me that the barrier for someone to build a tool they need to solve a problem is incredibly low.
The rush I used to get from coding has mostly faded, but I’m getting similar rushes managing different agents to build things now.
A blog post, not a product—no code, no tool, no demo to evaluate.
Another AI memory wrapper in a space already crowded by native provider features.
Mycelium-style bus lets parallel Claude sessions share context without a central orchestrator.
Another AI memory wrapper with no visible differentiation from existing context tools.
One command generates portable AI context—replaces manual re-explaining between models.
The product nails a painful micro-problem: turning sprawling chat logs into bite-sized, copyable context cards with explicit controls (Light/Balanced/Aggressive compression, token counts, BYOK for privacy). It’s a useful MVP — the UI signals care and control — but without obvious integrations or export targets (ChatGPT plugin, Slack, or API) it risks staying a handy one-off rather than a daily workflow tool.