A run receipt is proof of how a piece of agent work was done. It lists every step of one run in the order it happened, how long each took, which human gates a person approved and who, the branch each decision took, and each shell command with its exit code and — when the step captures its output with verifyHash — the SHA-256 of that output. Paste its badge into a pull request and the reviewer sees at a glance that the work went through your workflow, not around it.
Share one
- In the engine: open the finished run under Instances and click Share run receipt. You see the summary and anything removed before anything is uploaded.
- From your agent: it uses
ccw_share_run, shows you the receipt, and shares it only after you agree.
You get a link to the receipt page and a Markdown snippet with its badge for the pull request description. A run can be shared once; sharing it again returns the same link. Only finished runs — completed, failed or cancelled — can be shared, and a failed run makes an honest receipt too.
What a receipt never contains
Agent output, prompts, variables and run input are left out entirely — they routinely hold code, paths and secrets. The few texts a receipt does carry (the workflow's and steps' names, shell commands) are scrubbed of credentials, secret-looking values and your home directory, like a shared workflow.
What it proves
A receipt is recorded by your licensed engine while the run happens, attributed to your account, and cannot be edited after it is shared. The engine gives the agent one step at a time and does not move on until each step reports back; gates wait for a person. Output hashes let anyone who has the captured output check it byte for byte. Step-backs during the run are counted on the receipt, never hidden.
Delete a receipt from its page, or see all of yours on your shared workflows page. For the repository as a whole, add the CodyCody badge to your README.