How do I get a receipt for work done in Windsurf?
Add the Zambo connection to Windsurf, then run the work through it. Steps are saved as verifiable receipts as they execute, with results and source states, and the job closes into a handover your client or lead can open and check. Work done outside the connection leaves no receipt, so route client work through it from the first step.
Windsurf's agent writes and edits code inside your project, which makes its work unusually consequential and unusually hard to evidence: the diff shows what the code became, not which steps ran, what was checked, or what the agent tried and discarded. The receipt comes from the layer the work runs through, the same as for every supported client.
Setup is the standard add: https://zambo.dev/mcp as a connection, by the path the /add/ page shows for Windsurf. From then on, work the agent drives through the connection's tools is saved step by step (AER-1 receipts, IETF Internet-draft-zambo-aer1-21). Investigation steps carry their source states; change steps carry their saved results; the finished job reads at /today and delivers as a handover beside the pull request.
The boundary deserves emphasis for coding work: edits the agent makes entirely outside the connection are not in the record. Keep the connected session as the working session for client repositories, and enter any manual changes as steps in the same job. The record then matches the repo's story instead of telling a partial one beside it.
Checklist: your first Windsurf receipt
1. Add the Zambo connection in Windsurf from the /add/ page. 2. Open the client repository in the connected setup. 3. Assign a small, real task. 4. Let the steps run through the connection's tools. 5. Read the job's steps at /today; note the source states on investigation steps. 6. Check one receipt at https://zambo.dev/verify/ . 7. Attach the handover link to the pull request or delivery message.
Worked example
Sample: a bug fix in a client repo runs as a five-step job: reproduction, code search (sources resolved), the edit, the test run, and a summary step. The reviewer opens the handover beside the diff and sees not only the change but the checking that surrounded it, including the test step's saved result. (Sample scenario; no live record is cited.)
Frequently asked questions
Does the receipt replace the git history?
No. Git records the code's evolution; the receipt records the work: the steps, the checks, and the agent's path to the change. Reviewers use both, the diff for the what, the record for the how and the whether-it-was-checked.
Can my client check a Windsurf receipt without Windsurf?
Yes. The handover opens in a browser and receipts recompute at the public verify page. The client's check depends on the record, not on your editor.
What about pair work where I edit half the code by hand?
Add your manual changes as steps in the same job, labelled as yours. The record then shows the real division of work, which is what a lead or a client is actually asking about.
By Brennan Zambo, founder of Zambo.
Last verified: 2026-10-17.
Try a handover
A handover gives your client one proof link with verifiable receipts to review, then Accept or Flag.
try it: say 'use zambo to hand this over to <client>' in your ai