Roadmap
Nexus-Catalyst is a memory layer that follows you across the AI tools you use. This page is where it’s going. No dates — priorities move with what you tell us — but the direction doesn’t.
What’s live today.
- Signups are open. Every plan starts with a 14-day trial.
- Team memory. On a Team plan, what a teammate decided yesterday is in your session today. Anything marked private stays private — per memory, per project, or for your whole account.
- Eight clients documented end to end — Claude Desktop, Claude Code, Cursor, ChatGPT, Codex, Grok, Perplexity, and any MCP client by URL.
- Every memory knows which tool wrote it — the foundation for what’s next.
Hand a task to your next tool. Tell ChatGPT “have Cursor add the retry”, and your next Cursor session opens with that task at the top of recall — who left it, when, and what they meant. Tasks expire (24 hours by default) so a queue never becomes a junk drawer, and the first tool to see one claims it, so two windows don’t both do the work. A handed-off task is shown to you, not executed for you: your tool asks before it acts.
Decisions have a lineage. When a new decision replaces an old one, recall says so — this superseded that on the 3rd — instead of returning both and letting the model pick. The knowledge graph already holds the structure; this surfaces it.
Retention you set. Forget after N days. Never store from this repo. Redact anything matching a pattern before it’s written. Rules, not a checkbox.
Don’t start empty. Import what you already have — a ChatGPT memory export, Claude project files, a folder of markdown — so day one has context in it.
Know the project without being told. Hooks already see the repo, the branch, the working directory. Recall should scope itself from that instead of relying on a conversation id you have to keep tidy.
Install from the directory. Add Nexus-Catalyst from your client’s own connector list instead of pasting a URL.
Deeper integrations. GitHub issues and pull requests as memory context; decisions captured from Slack threads.
What we won’t do
Section titled “What we won’t do”- Train on your data. Your memories are retrieved, never learned from.
- Trap it. Export is complete, in plain formats, whenever you want it. The memory is portable by design — that’s the product.
- Act on your behalf. A memory, a hint, a handed-off task: each is shown to the tool as information. What happens next is between you and your tool.
Something missing? Tell us.