Handover from Grok to ChatGPT

Grok and ChatGPT share nothing: no memory, no files, no record crosses between xAI and OpenAI on its own. A job that starts in Grok, maybe for the live search or the speed, and needs to finish in ChatGPT dies at the border unless someone retypes it. A Zambo HANDOVER moves the job itself from Grok to ChatGPT as one checkable record: the goal, the finished steps with a verifiable receipt for each, the decisions, and the exact next step. The receiver in ChatGPT starts from the record, not from a summary of it. HANDOVER is Zambo's flagship product.

Before you start: Zambo on the Grok side

Zambo connects to Grok as a remote MCP server at https://zambo.dev/mcp: add it as an MCP server in Grok, or in a Grok bot stack that accepts MCP servers, and the tools appear in the session. There is no key and no local install on the Zambo side: it is a hosted remote server.

Full setup: Add an MCP server to Grok. The free tier is 20 calls and 1 wrap-up free every day. Work run through Zambo in Grok saves a verifiable receipt per call as it runs, and those receipts are what the handover carries.

Step 1: finish the Grok side and create the handover

Do the work in Grok through Zambo tools, so each finished step has its receipt saved at the moment it ran.
At the end of the Grok session, say: hey zambo, wrap up this session. Zambo assembles the handover as a single record, goal, what is done, what is next, every decision, and the receipts attached, and returns a link in the pattern https://zambo.dev/handover/ followed by the handover ID, plus a short continue code. Send that one link to whoever continues the job in ChatGPT. Nothing else needs to be copied across: no recap, no pasted chat history.
Open the returned handover link yourself before sending it on. Check the goal reads the way the job was commissioned, the next step is exact, and any step nobody verified is named as not checked.

Step 2: connect Zambo on the ChatGPT side

In ChatGPT on the web, open Plugins, select the plus button, then Add custom MCP server, name it Zambo, enter https://zambo.dev/mcp under Connection, configure authentication as ChatGPT presents it, accept the risk warning, and select Create as a plugin. Then install the plugin from your personal plugins or your workspace before using it. Custom MCP servers are added on ChatGPT web, not on mobile.

Full setup: Add Zambo to ChatGPT. New to Zambo on either side? The bridge page walks the whole install: Add Zambo to your AI. Picking up a handover in another AI is always free: the pickup never counts against the free tier.

Step 3: open the handover in ChatGPT and continue

Open the handover link in your browser first and read the record: the goal, the finished steps with their receipts, the decisions, and the exact next step.
In ChatGPT, make sure the Zambo plugin is installed and active for this conversation.
Paste the handover link into the chat, or use the short code from the Grok side and say: continue my zambo session, followed by the code. Then tell ChatGPT: open this handover, check the receipts that carry weight, record accept or flag on the handover, then continue from the recorded next step.

What travels in the handover

The goal. The job in the words it was commissioned in, so ChatGPT continues the same job and not a retelling of it.
The state. Each finished step, with the verifiable receipt saved when that step ran in Grok: the tool that ran, the recorded inputs, and the saved result.
The receipts. One public receipt link per finished step, checkable by anyone with no account. Receipts from a real Zambo session, the shape that travels:
- Receipt d81aeb41: capability_search: the session finds the right tool first
- Receipt 26b353a9: live_price: the BTC price, with CoinGecko named as its source
- Receipt 1f56fe3e: journal_log: the finding written into the job record
That session is written up end to end in a receipt for this conversation.
The decisions. Every decision made along the way, with its reason, so the receiver does not quietly re-argue what is already settled.
The next step. Stated exactly, before the transfer, so momentum survives the switch from Grok to ChatGPT.
What was not checked. Sources or steps nobody verified are named as not checked, not smoothed over.

What does not travel

The raw Grok transcript. The record carries the job, not the chat. Small talk, dead ends, and anything that never became a step stay behind.
Work done outside Zambo. Steps the Grok session ran with other tools or by hand have no receipt, so they are named as not checked in the record instead of travelling as fact.
Tool access itself. The handover does not grant ChatGPT anything: the receiving side needs its own Zambo connection, which is the setup in Step 2.
Files that were never attached to the record. If a file matters to the next step, attach it to the job before wrapping up, or name it in the next step so the receiver fetches it deliberately.

Verify note

Before accepting, open one or two receipt links from inside the handover and paste each receipt ID into zambo.dev/verify. A match confirms the saved result was not changed since it was saved. That is what a receipt proves: the record is intact, not that the work was right. Judging the work is the receiver's job, now done against the record instead of a recap. Then record accept, or flag what is wrong, on the handover itself. The transfer is not complete until that decision exists.

Why not just paste a summary into ChatGPT?

A summary is narration: it can skip the step that failed and drop the decision that constrained everything after it, and none of that is detectable later. The handover record fixes each step under its receipt at the time it ran in Grok, so ChatGPT can recompute any step instead of believing it. The general pattern is on the flagship page: AI agent handover, and the full continuity picture is in the cross-AI continuity guide.

Cost of the switch

The wrap-up and the pickup are the free tier's home ground: 20 calls and 1 wrap-up free every day, and picking up in another AI is always free. Heavy days exist too: the Day Pass is $0.99 for unlimited use for 24 hours, no subscription.

More handover recipes

A handover is only as strong as the receipt the receiving side can check. The AER-1 badge kit carries that same verifiable-receipt proof outward, as an embeddable badge for the pages and profiles where the work is shown.