ZAMBO.

Direct answer

The morning standup: what your agents did overnight, with receipts

Your agents ran overnight: a price watch, a digest, an inbox triage, each in its own process, each gone by morning. What did they leave you? Three paragraphs in three chat logs, written by the agents themselves. One says all clear. Which prices did it actually see? Did the digest send that story yesterday as well? Nobody can check, so the morning standup turns into an interrogation, and the work of the night gets graded by the worker who did it. The standup on this page runs the other way: every overnight job ends by wrapping a handover, and the morning opens with a pickup, reading the steps and receipts the night actually left. The standup stops being an investigation and becomes a read.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated November 2, 2026. First published November 2, 2026. The worked example below is a real run executed against the live service on November 2, 2026, with every receipt read back from the service the same day.

The interrogation tax

An overnight agent's summary is a claim, and claims compound badly. The watch agent that missed a move writes the same all clear as the one that genuinely saw a quiet night, and the two are indistinguishable in a log. The digest bot cannot prove it did not repeat itself, because nothing outside its process recorded what it sent. The triage agent's "handled it" covers anything from a careful reply to a deleted thread. So the operator re-reads raw logs, re-runs spot checks by hand, and still ends up trusting the summaries for everything they did not personally re-verify. That is the tax: the standup, the one meeting meant to coordinate the day, spends itself auditing the night with tools too weak to audit anything. Records end the tax at the source. When each call of the night carries its own receipt and the run ends sealed into a handover, the morning does not ask the agents what happened. It reads what happened.

The pattern: the night wraps, the morning picks up

1. The night shift wraps

The last step of every overnight job is handover: a plain summary of what was done, the steps with their receipts, and the next steps written for the morning. Wrapping is the day's free wrap-up, so the habit costs the night nothing extra. The scheduled agent heartbeat recipe builds exactly this wrap into the loop a cron-driven agent runs, so the standup's raw material exists by construction, not by an agent remembering to be tidy at 3 a.m.

2. The standup opens with a pickup

Whoever runs the standup, the operator or an AI asked to prepare it, starts with continuity_get_recent: the job's saved steps, the receipts they carry, and the handover the last run left, including the next steps it wrote. Pickup is free, and picking up in another AI is always free, so the standup can be prepared in a different app than the one that ran the job and still read the identical record. No re-briefing, no forwarding of logs, no "paste me what happened."

3. Read the stream, not the summaries

The public receipt stream lists the night's calls in the order they happened, across every job. Each step opens to its own receipt page at zambo.dev/run, where the saved result can be checked by anyone holding the link. The standup samples what matters: the alert that fired, the send that looks repeated, the number that moved. And a job that ran without wrapping shows up as exactly what it is, calls with no handover over them, a visible gap instead of a smooth summary.

4. Decide on the record

Standup decisions attach to specific receipts, so "approved," "why did this fire," and "do not send that again" point at steps anyone can reopen. The morning's own output, the day's priorities and the questions still open, gets written back as the next handover in the chain, which is what the following standup picks up. The meeting becomes short because its evidence arrived before it started.

One overnight run, executed live on November 2, 2026

To keep this page honest, the overnight half of the pattern was executed for real before the page was written: a fresh agent identity, created for this run and named overnight-standup-run-2026-11-02, running a small watch job. The job: check BTC and ETH, and alert only on a move of 3 percent or more in 24 hours. What the night left, and what a standup would pick up in the morning:

The run, receipt by receipt

Why the accounting works

Count a standup. Pickup: free, always. The receipt stream: public. The tier the night runs on is the canon line: 20 calls + 1 wrap-up free every day. Picking up in another AI is always free. Each overnight job spends its own calls inside its own daily allowance, with the wrap consuming the free wrap-up rather than a call. So a standup over five jobs or fifty reads at the same price as a standup over one: nothing. The paid step appears where it should, inside the night, when a single job's work outgrows 20 calls before it wraps. That job is the Day Pass or Pass case, $0.99 for 24 unlimited hours or the Pass at $29 a month, and the standup still reads its record for free the next morning.

Why it compounds

One standup on records is a better meeting. A month of them is an operating history. Trends stop being recollections: the watch agent's baselines form a series across its handovers, so the standup compares against last week from data, not from someone's memory of last week. The digest that repeats itself is visible in its own receipts within a day, and the correction, once written into a next step, is picked up by the following run instead of re-argued every morning. A new operator, human or AI, comes up to speed by reading the chain rather than shadowing the logs. The night shift gets more trustworthy the longer it runs, because its record gets longer, and that record is the asset the standup is really building.

What a record does not settle

A verifiable receipt proves the saved result was not changed since it was saved; it does not prove the price was right, the alert threshold was wise, or the agent chose the right tool. A standup built on records makes an operation's history checkable, so judgment, the operator's, a client's, another AI's, can rest on a record that is not quietly moving. This page is general information, not legal advice.

Frequently asked questions

What is a morning standup for AI agents?

A morning standup for AI agents is the daily read of what the overnight jobs actually did, taken from records instead of from the agents' own summaries. In Zambo the standup reads two things at https://zambo.dev/mcp: continuity_get_recent, which returns each job's saved steps, receipts, and latest handover with its written next steps, and the public receipt stream, which lists the night's calls in order. Every overnight job that ended by wrapping a handover shows up as checkable steps, so the standup starts from evidence and spends its time on decisions.

How does the standup read what agents did overnight?

The standup opens with a pickup: continuity_get_recent returns the job's recent steps and receipts plus the handover the last run left, including the next steps it wrote for the morning. The public receipt stream gives the full night in order, and any step opens to its own receipt page, where the saved result can be checked. Pickup is free, and picking up in another AI is always free, so whoever runs the standup, the operator or an AI in a different app than the one that ran the job, reads the same record at no cost.

What does the standup cost?

The reading is free: pickup never tolls the day and the receipt stream is public. The overnight jobs pay for themselves out of their own allowance, 20 calls + 1 wrap-up free every day, and the wrap at the end of a run is that day's free wrap-up, so a standup over a fleet of wrapped jobs costs the morning nothing. The worked example on this page used 2 of the 20 calls for its work. A job whose night outgrows 20 calls is the Day Pass case: $0.99 makes the endpoint, https://zambo.dev/mcp, unlimited for 24 hours including unlimited wrap-ups, no subscription: get the Day Pass. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders.

What if an overnight agent did not wrap its work?

Then the standup sees the gap, which is itself useful. The receipt stream shows the job's calls, but with no handover there is no sealed summary, no written next steps, and nothing to pick up: the agent's report is a claim in a chat log and the standup has to take its word. The fix is procedural, not technical: wrapping is the last step of the job definition, the way the scheduled agent heartbeat recipe builds it in, so a missing wrap reads as a defect in the run rather than a mystery about it.

What does a receipt settle at a standup?

A receipt proves the saved result was not changed since it was saved, and anyone at the standup can run that check from the receipt page. It settles what the run did and what it saved: which price the watch agent saw, which stories the digest sent, which messages the triage touched. It does not prove the agent's judgment was right: whether the alert threshold was wise or the right story led the digest is a decision the standup still makes, now on a record that is not quietly moving underneath the argument.

Related

The Loop kit

One routine, every piece of it in one place: the data that found the loop, the recipe, the two shapes a daily loop takes, and a starter repo with Zambo already wired in.