Handover from Goose to Open WebUI

A job started in Goose rarely has to finish there. A Zambo HANDOVER moves the job itself to Open WebUI 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 Open WebUI starts from the record, not from a summary of it. HANDOVER is Zambo's flagship product.

Before you start: Zambo on the Goose side

Run goose configure, choose Add Extension, then Remote Extension (Streamable HTTP), name it zambo, and enter https://zambo.dev/mcp as the endpoint URI. Or add a zambo entry under extensions in ~/.config/goose/config.yaml with type streamable_http, uri set to https://zambo.dev/mcp, enabled true, and timeout 300. The type must be exactly streamable_http and the address must sit under uri: a url field will not load. Extensions apply to new sessions, so start a fresh session after configuring.

Full setup: Add Zambo to Goose. The free tier is 20 free calls per day. Work run through Zambo in Goose saves a verifiable receipt per call as it runs, and those receipts are what the handover carries.

Step 1: finish the Goose side and create the handover

Do the work in Goose through Zambo tools, so each finished step has its receipt saved at the moment it ran.
At the end of the Goose session, give one wrap up instruction: hand this job over with the goal, what is done, what is next, every decision, and the receipts attached. Zambo assembles the handover as a single record and returns a link in the pattern https://zambo.dev/handover/ followed by the handover ID. Send that one link to whoever continues the job in Open WebUI. 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 Open WebUI side

MCP servers in Open WebUI are admin only. On Open WebUI v0.6.31 or later, an admin opens Settings, then Admin, then Integrations, clicks + Add Connection under External Tool Servers, sets Type to MCP (Streamable HTTP), enters https://zambo.dev/mcp as the Server URL, sets Auth to None, and saves. Use the MCP connection type, not OpenAPI: the wrong type can leave the interface stuck on a loading screen.

Full setup: Add Zambo to Open WebUI. New to Zambo on either side? The bridge page walks the whole install: Add Zambo to your AI.

Step 3: open the handover in Open WebUI 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.
Open a chat in Open WebUI, click +, then Integrations and Tools, and enable the Zambo tool for this chat. The admin connection alone does not switch Zambo on inside a conversation.
Paste the handover link into the chat and say: 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 Open WebUI 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 Goose: 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 Goose to Open WebUI.
What was not checked. Sources or steps nobody verified are named as not checked, not smoothed over.

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 Open WebUI?

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 Goose, so Open WebUI can recompute any step instead of believing it. The general pattern is on the flagship page: AI agent handover.

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.