Show a client what the agent did.
When a client asks what they paid for, send them the session: every command, edit and failure, with your keys and paths masked.
The problem
More client work is done with coding agents, and clients reasonably ask what happened. A hand-written summary takes time and asks the client to take your word for it. Raw logs are unreadable, and they are full of things the client should never see: API keys, tokens, your home folder, other projects on your machine.
What you want is a readable record of the session that you have checked, with the private parts taken out.
How Postrun handles it
- STEP 01
Record the work on your machine
Run your Claude Code or Cline session as usual while Postrun records it. Everything stays in
~/.postrunon your computer, readable only by your user account. Nothing is sent to us or to the client. - STEP 02
Review it yourself first
Open the session in the review app. Check the timeline, the files the agent created, edited or read, the commands it ran with their exit codes, and the edits as diffs. You know what the report will say before anyone else reads it.
- STEP 03
Export one session
Export writes one HTML file. Before it is written, Postrun masks known secret formats, credential values and home folder paths, and leaves out your machine name and local capture paths.
- STEP 04
Check every mask
The export lists every value it masked, with where it was and the text around it, so you can confirm nothing slipped through. Redaction is a safety net, not a guarantee, so skim the report before you send it.
- STEP 05
Send the file
Email it, attach it to an invoice or drop it into the client's chat. It opens in any browser with no account and no install. It runs no JavaScript and loads nothing from the internet, so it is safe for the client to open.
Before you send it
- A report is the whole session. It includes your prompts and the agent’s replies, not only the result. Read it the way the client will.
- Cost is included when the agent reported it. If the session has cost figures, the report shows them. Decide whether that is something you want to share.
- Redaction catches secrets, not business context. It masks keys, tokens, passwords and paths. It doesn’t know that a file name or a comment mentions another client.
- One session per report. A piece of work that spans several sessions becomes several files.
Open the example report to see exactly what a client would receive.
Give clients the record, not a recap.
Postrun is in early access for Claude Code and Cline. Open the example report to see exactly what an export looks like, or join the waitlist for the install.