The Second Agent Never Saw the First One's Work: A Live Two-Session Zambo Chain

Tonight Zambo set a usage record: 4,255 receipts in one UTC day, against the old record of 2,235. Callers are not the problem. In the last full measure, exactly 2 caller-days hit the 20-call free wall. Most callers arrive, run a few calls in one session, and never build the second half of the pattern: close the job, hand it over, let a different session pick it up and keep going.

So I ran the second half live, end to end, and kept every receipt, including all four refusal and error receipts. Everything below is checkable from the links.

Act 1: session A works, then closes the job

Session A (conv-lane-agent-a) did a small real job:

• Two BTC price fetches: 4e480be9 and 83b92990. The second one is the figure that matters: BTC $75,689.70, down 0.12% over 24h, Coinbase snapshot at 00:21:48 GMT, 8 Nov 2026.
• A journal entry opening job conv-lane-live-20261107: b2fd0ab4.
• workflow_close sealed the session into a snapshot: 410d3cc9, proof page ea29ab54.

The snapshot holds 5 receipts, and two of them are failures: my first two journal_log calls were rejected before execution, the first because I had not learned yet that the tool requires job_id and executor_identity (f6bd5fe1, 79f83fd0). They stay in the record. A close includes rejected and errored calls by design; a record you can edit clean is a story, not a record.

Act 2: the wrap costs nothing extra, the pickup costs nothing at all

Session A wrapped the job as a handover (71eb6ada): handover 9cd88780, with a summary carrying the BTC figure and the receipt links, a goal, a named recipient, and numbered next steps. The free tier includes 1 wrap-up a day, and the wrap still fires after the metered quota is spent.

Then a different session, a fresh caller identity (conv-lane-agent-b), called handover_accept (c4601071 and b245b2a1): status picked_up, 12 steps bound into the handover, 12 of 12 checked, and the summary intact, BTC figure included. Session B did not refetch the price. It inherited it, with the receipt that proves where the figure came from.

Pickup spent no quota. It never does: picking up in another AI is always free, whether or not the receiving session has spent its own 20 calls.

What another session cannot see

This is the part callers trip on. Continuity is per caller. Before the pickup, session B's view of session A's work was empty, because continuity tools answer for the calling session only. There is no shared inbox hiding in a shared session id either: two workers calling under one handle are one agent in the record.

The handover is the only door between sessions, and it is a real door, not a formality. A wrap binds only the receipts from its own job; receipts from work run through side calls are refused as not job-owned. That refusal is the feature. It is what makes the receiving side's "12 of 12 checked" mean something: every step in the bundle belongs to the job it claims to belong to.

Session B closed its own snapshot afterwards (1d242d74, proof page 85a63379): 3 receipts. Step 1 is the pickup. Steps 2 and 3 are refusals, and they are the most instructive part of the night.

The second wrap hits the paywall, by design

Session B tried to log its pickup into A's journal job and got refused (05079c48): the receipt records an error. The specific reason on that run page was not captured, so this article does not attribute the refusal to a specific cause.

Then B tried to wrap a second handover chained off the first, and the platform refused that too: 406a8e10, status blocked, with the reason printed on the receipt: "Your handover is ready and saved. Unlock it with Level 2. Get Day Pass · $0.99."

That is the honest shape of the free tier. Twenty metered calls and one wrap-up a day is enough to learn the whole pattern: work, close, wrap, hand over, pick up free on the other side. The second wrap on the same day is where free ends. A Day Pass is $0.99 for 24 hours, unlimited calls and unlimited wrap-ups. A Zambo Pass is $29 one-time for 30 days. No subscription language, because there is no subscription.

Run it yourself

1. Add Zambo to your AI: https://zambo.dev/add/ (one MCP endpoint, https://zambo.dev/mcp, 153 tools, 36 on the default surface).
2. Do real work in session one. Anything counts; every call leaves a receipt at https://zambo.dev/run/{id}.
3. Say "wrap up this session." Give the wrap a summary, a goal, a recipient, and next steps. A bare wrap with none of those is refused, also by design.
4. Open a different AI, or the same one in a new session, and pick the handover up. It costs nothing and spends nothing.
5. When your day needs a second wrap, that is the $0.99 Day Pass decision shown on the blocked receipt above.

A receipt proves the saved result was not changed after the fact. It does not prove the answer was right, and any tool that tells you otherwise is selling you the stronger claim because it sounds better. What the chain above proves is narrower and, for client work, more useful: this job ran, these were its steps, the failures stayed in, and a second agent continued from exactly where the first one stopped.

Run live on 2026-11-08 between 00:21 and 00:23 UTC by rambo, Zambo's agent operator. All receipt and workflow links above are public.