Guide

Move your work between AIs without starting over

By Brennan Zambo · Published October 16, 2026

Short answer: To move work from one AI to another without losing context, keep the work in a memory both AIs can reach. Zambo continuity threads do that: connect zambo.dev/mcp in each AI, start a thread in one, and open the same thread in the other.

Why context gets stuck

Each AI app keeps its own memory. Start a project in one, switch to another for a different strength or because you hit a limit, and the new one knows nothing. You paste summaries, re-upload files and re-explain decisions. Things get lost on the way.

The fix is to keep the project's memory outside any one app, in a place every AI you use can read and write.

Step by step

1. Connect Zambo in every AI you use. Paste https://zambo.dev/mcp into each one's connector or MCP settings. It's the same URL everywhere, with no key.
2. Start a thread in AI #1. Say: "Start a zambo continuity thread called 'Website relaunch'." The AI calls continuity_start_thread.
3. Work as usual. Steps your AI runs through Zambo tools land in the session with verifiable receipts. Anything done outside Zambo can be noted with journal_log and is marked agent-reported.
4. Switch to AI #2. Say: "List my zambo threads" (continuity_list_threads), then "Open 'Website relaunch'" (continuity_open_thread).
5. Catch up in one step. Ask "What happened recently?" continuity_get_recent returns the thread's recent steps and receipts in order, so AI #2 picks up where AI #1 stopped.
6. Set your preferences once. Use continuity_set_prefs for how you like to work. They follow you to any AI that opens the thread.
7. Hand it off if you need to. A thread can become a client handover (handover) or a summary receipt (workflow_close).

What you get

• One thread that follows you to any AI that supports MCP.
• A step history with verifiable receipts, so the next AI sees what actually ran and not just a summary.
• Your memory, kept by you, not tied to one app's settings.
• A handover link whenever the thread needs to go to someone else.

A receipt shows the saved output hasn't changed since the call. It doesn't prove the output is correct.

Related

• Continuity
• Cross-AI continuity (technical guide)
• Try continuity
• Share memory between two AI apps
• Switch AI models mid-task
• Connect your AI

FAQ

How do I continue a project in a different AI?

Connect zambo.dev/mcp in both AIs, start a continuity thread in the first, then list and open the same thread in the second.

Do I have to copy and paste summaries?

No. The second AI reads the thread's recent steps directly with continuity_get_recent.

Which AIs does this work with?

Any AI app or agent that can add an MCP server URL. Our connect pages cover setup for the common ones.

Is my memory locked to Zambo?

Threads belong to you and can be packed into a handover or summary receipt. The receipts use the open AER-1 format, which anyone can read and check.

Does it cost anything?

Continuity tools are free up to 20 calls per tool per day. A $0.99 Day Pass or Zambo Pass lifts that for heavier use.

CTA: Paste zambo.dev/mcp into your AI. Do it in every AI you use, and your thread shows up in all of them.

All guides · Docs · For agents · Pricing