How do I get receipts for AI work in Cursor without changing my workflow?
Add the Zambo connection to Cursor once, and keep working exactly as you do now. Work that runs through the connection is saved step by step as verifiable receipts, so a coding job ends with a checkable record: what ran, what it produced, and what was never checked.
The change is deliberately small: one MCP connection, https://zambo.dev/mcp , added to Cursor's settings. Your editor, your models, your prompts, and your review habits do not change. What changes is that the work stops evaporating. Each step the agent takes through the connection is saved as an AER-1 receipt (IETF Internet-draft-zambo-aer1-21) at the moment it runs.
That record answers the questions a coding job actually raises. What did the agent change, and in which order? Which checks or sources were behind a claim in its summary, and which steps are marked not checked? When a client or a teammate asks what the AI did to the codebase, the answer is a link to the step record, not a retelling.
The buying test is one job: connect, run a small real task, then open the record and check one receipt on the verify page. If the record reads the way your work felt, the setup has already paid for its five minutes. Work done outside the connection, in a plain chat with no tools, is not recorded; the receipt covers what ran through it, and says so.
Checklist: Cursor receipts in five minutes
1. Open Cursor settings and add the MCP connection: https://zambo.dev/mcp . 2. Start a fresh agent session and give it a small, real task. 3. Let the agent work through the connection's tools. 4. Open the job's record and read the steps in order. 5. Pick one receipt and check it at https://zambo.dev/verify/ . 6. At delivery, send the client the handover link for the job instead of a summary paragraph.
Worked example
Sample: a developer asks the agent to add input validation to a form handler and run the tests. The record shows the edit steps, the test step with its saved result, and one step, a documentation lookup, marked not resolved. The summary said "validation added, tests pass." The record says the same, and shows its work, including the gap. (Sample scenario; no live record is cited.)
Frequently asked questions
Does this slow the agent down?
The recording happens as steps execute, inside the same calls the work already makes. In practice the setup cost is the five minutes of connecting; the per-job cost is not something developers report noticing.
Are my code and prompts sent anywhere new?
The connection records the steps of work run through it: the tool, the saved result, the states. It is a work record, designed to be shown to clients, so treat connected work the way you would work you intend to hand over.
What if the agent works in Cursor but a step runs outside the connection?
Then that step has no receipt, and the record shows the gap rather than papering over it. Route the steps that matter through the connection, and read not checked labels as your review list.
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