Zambo, the verifiable work layer for AI

Move work from Claude to ChatGPT (and back) without starting over

Add Zambo to your AI

Finish the work in Claude, then package it as one handover link carrying the step-by-step receipts. Copy the handover into ChatGPT to continue, or send the client their separate client link so they can review the work and respond.

Deliver Claude's recorded work to ChatGPT or a client

  1. In Claude, ask Zambo to package this job as a handover, including what was not checked.
  2. Open the returned handover link and review what will be shared.
  3. Use the page's copy action to copy the handover, then paste that copied handover into ChatGPT. Do not paste just a vague summary.
  4. For delivery, send the separate client link to the reviewer. Only its holder can Accept or Flag. An acceptance records their decision and its date; a flag records the issue.
  5. Open each step's verifiable receipt at the public verifier.

For a chain, pick up the preceding handover with handover_accept and use continue_from in the same job session. For recurring work, handover_series creates a living handover link. A client decides Accept or Flag through their separate client link. Public example pages cannot record your decision.

Bring ChatGPT's delivery record back to Claude

To continue ChatGPT work in Claude, ask Zambo for a handover in ChatGPT, open it, copy the handover using its copy action, then paste that copied handover into Claude. Keep the receipts and not checked list attached. Continue the job as a chain if you want both parts on one record.

Inspect a public client-delivery example

bd7e5325-33fd-4c5e-b029-76b781fa2f51 is an open public handover with five steps. Its work-level not checked list names aa725980 and 75253fbc. Those are work gaps, not failed saved-byte checks. The public page shows steps, verifiable receipts, and what the record proves and does not prove. Its public view is read-only.

What this record proves, and what it does not

A receipt proves the saved result was not changed since it was saved. It never proves the answer was right and never proves an external event happened.

A handover does not establish who produced the work. AI labels and reviewer details are reported claims, not verified identities. Spot-check important outside outcomes separately.

Start a handover, or keep private project context

Start your own handover. For the private memory side, use Zambo continuity. This page is about client delivery and the Accept or Flag decision, not a replacement for the general continuity guide.

Questions and answers

How do I move work from Claude to ChatGPT with a client handover?

Ask Zambo in Claude to package the job as a handover. Open the link, copy the handover using the page's copy action, and paste that copied handover into ChatGPT. Send the client their separate client link for a decision.

How do I continue ChatGPT work in Claude with its receipts?

Create the handover in ChatGPT, open it, copy the handover from that page, and paste the copied record into Claude. A chain keeps the later work connected to the original receipts.

How do I move a project from ChatGPT to Claude for client delivery?

Move the recorded work through a handover, then give the reviewer their separate client link. For shared private context rather than delivery, use the continuity page.

What does the receiving AI or client see on the handover?

They see the shareable work record: steps, receipt links, and work-level gaps. Review the public content before sharing it. The public view is read-only.

What do Accept and Flag record on a client handover?

The holder of the private client link records a decision and its date. Accept means acceptance from that recipient's point of view. Flag records a problem and reason. Neither proves the work was correct.

What does a copied handover prove, and what does it not prove?

A receipt proves the saved result was not changed since it was saved. It never proves the answer was right and never proves an external event happened. It also does not prove the producer's identity.

What does the handover cost?

Public handover page: Yes on Free and Zambo Pass. Browser verify and Accept or Flag: Yes on both. A Day Pass ($0.99 for 24 hours) lifts it. Zambo Pass $29 for 30 days, one payment. Sealing, including producing the dispute pack, requires a pass. Current terms are at https://zambo.dev/pricing/.

Add Zambo to your AI

Connect the free MCP at https://zambo.dev/mcp in Claude, ChatGPT, Gemini, Cursor, Grok, Windsurf, or VS Code. No key is needed. The first receipt arrives with the first call through Zambo. Adding a URL does not automatically install a connector; use your client's MCP settings.

More AI agent answers · Try the demo · Current pricing and tool-specific limits

Add Zambo to your AI