Docs
Receipts
Inspect the durable record created for state-changing actions.
What a receipt records
Every action that changes state ends as a receipt: the action taken, the inputs it ran with, the cluster it touched, the signature when a transaction was involved, and a timestamp. Receipts are generated locally and signed on your machine.
Why receipts
Agents work fast and in parallel. Receipts turn that work into something you can review after the fact: what shipped, what signed, and what was only proposed. Approval decisions stay attached to the actions they authorized.
Where they live
Receipts collect in the console next to the session that produced them, and can be inspected or shared from there. Nothing is uploaded unless you share it.