Receipts
Every finished piece of work has a receipt: what was asked, who did it, the verdict, the steps, the files, what needed your OK and how it was checked. You can share it as a read-only link.
Updated 2026-10-17
Open Receipt under any delivery card in a chat. It shows the run as Pythe recorded it, not as the agent described it.
What a receipt shows
- The goal, who did it, when it finished and how long it took.
- The verdict in plain words (Delivered, Partly done, Not delivered, Did not finish), decided by the server.
- The steps, as plain verbs such as “Searched the web” or “Made a file”, with how many failed. Never the inputs the agent used.
- The files: name, type, size, what was counted when read back, and a picture of the first page when there is one.
- Each action that needed your OK, and what you decided: approved, edited then approved, said no, or done without asking by your rule.
- The checks that passed and failed, from the delivery verdict.
What is always left out
- Email bodies and message texts. An email shows only its subject.
- Keys, tokens and passwords, and the query string of every link.
- Email addresses, unless you tick Show email addresses.
- The names of custom tools (shown as “Used a custom tool”).
Share a receipt
- Open the receipt and switch on Share receipt.
- Copy the link. Anyone with it can read the receipt at
/receipt/…. It is not listed in search engines. - Tick Include files to let visitors download the files. Without it they see names and pictures only. Downloads use links that expire after 10 minutes.
- Switch it off at any time. The link then shows that the receipt is not available.
The link shows the receipt as it was when you shared it. Later changes to the run do not appear unless you change a share setting, which takes a fresh copy.
Related
Previous: Autopilot and trust rules · Next: Guardrails around approvals