How do I get a receipt for AI work done in VS Code?
Add the Zambo connection in VS Code through the MCP configuration path (the /add/ page lists VS Code under Other), then run AI work through the connection. Each step is saved as a verifiable receipt as it executes, and the job becomes a handover link that proves the work to a client or a lead.
VS Code is where a large share of AI-assisted development actually happens, through its agent and extension surfaces. The editor shows you the session; it does not give the session an afterlife as evidence. As with every supported client, the receipt comes from the connection the work runs through, not from the editor that hosted it.
The add follows the generic MCP client path: one hosted connection, https://zambo.dev/mcp , configured once; the /add/ page carries the current steps for the Other category where VS Code sits alongside Windsurf. Work driven through the connection from then on is recorded step by step: investigation with its source states, edits with their saved results, test runs with their outcomes, each committed in an AER-1 receipt (IETF Internet-draft-zambo-aer1-21) at execution.
Keep the same boundary discipline as the Cursor and Windsurf pages in this cluster: work done in a disconnected session leaves no receipt, and manual edits belong in the job as steps labelled as yours. The reward is a delivery where the code review and the work review are the same meeting: the diff for the code, the record for the process.
Checklist: your first VS Code receipt
1. Add the Zambo connection through VS Code's MCP configuration (the /add/ page, Other category). 2. Restart or reload as the client requires and confirm the connection lists. 3. Assign a small, real task in a client repository. 4. Run it through the connection's tools. 5. Read the steps at /today; check one receipt at https://zambo.dev/verify/ . 6. Attach the handover link to the pull request or the delivery note.
Worked example
Sample: a refactoring task runs as steps: usage search across the repo, the rename edits, the build, the test suite, each with its saved result. The lead reviewing the pull request opens the handover and sees the test step's own output instead of a claim that tests passed. (Sample scenario; no live record is cited.)
Frequently asked questions
Which VS Code AI surfaces does this cover?
Any work you run through the Zambo connection from VS Code. The receipt follows the connection, not a specific extension, so the setup survives your choice of assistant inside the editor.
Is the setup different from Cursor's?
The pattern is identical (one hosted connection, added once) and only the configuration screens differ. The /add/ page keeps the per-client steps current; VS Code is listed under Other alongside Windsurf.
Can a receipt cover a debugging session?
Yes, and debugging sessions are high-value records: the investigation steps, the hypothesis checks with their results, and the fix step together show a lead exactly how a hard bug was cornered.
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