Agents can do the work. Can they show it?
Coding agents now open pull requests on their own: they read the issue, change the code, run the tests and ask for review. The hard question has moved. It is no longer whether an agent can make the change; it is how the person who merges it knows the change works.
Today the answer is mostly "trust me", plus a screenshot. We think that has to change before teams can hand agents more of their work. attested is our first step.
Screenshots are the wrong kind of proof
Your tests already record proof that your app works: screenshots, videos, and step-by-step traces of every click. When an agent wants to show a reviewer, it copies some of that out and pastes it into the pull request, or posts it somewhere it can link to.
That goes wrong in public. On 30 September, Help Net Security reported Glow Labs' PixelLeak research: more than 13,000 internal screenshots that coding agents had pushed to public GitHub, across more than 900 repositories and 300 organizations.
Leaks are only half of it. A screenshot shows one moment. It does not say which version of the code produced it, which tests ran, or who made it. Pasting proof around makes it both riskier and weaker.
Swap the screenshot for a receipt
attested keeps the proof where your tests saved it, in your CI run, and gives the pull request a signed receipt instead. It works with the Playwright tests you already have, or any test runner that writes a CTRF report.
The receipt gives you four things:
- A straight answer. The tests passed or failed, on this exact commit.
- A claim ticket. Every screenshot, video and trace is one command away, whenever you want it.
- Proof nothing changed. The receipt holds a fingerprint (a sha256) of every file. Edit one byte and it no longer matches; alter the receipt and its signature fails.
- A gate. A required check blocks the merge unless a signed receipt says the tests passed.
Think of a coat check: you don't carry the coat around, you get a ticket, and the ticket gets you exactly that coat back.
The signing happens in a separate job that never runs the pull request's code, and the check that enforces it runs from a pinned commit the pull request can't change. attested also helps agents get there: when a test fails, it hands the agent a short failure packet (what broke, where, and what to run again, with emails and tokens masked), so the agent can fix the problem instead of guessing.
Evidence is what lets autonomy grow
At Praxso we talk about governed autonomy: giving agents real room to act, inside rules a team can see and enforce. Room and rules are not opposites. The more an organization can verify what an agent did, the more it can safely let the agent do.
Evidence is the bridge. A receipt turns "the agent says the tests pass" into something a reviewer, a team lead or an auditor can check later, without re-running anything and without taking the agent's word for it.
Requiring receipts on merge turns a good habit into a rule, applied the same way to every pull request, whether a person or an agent wrote it. That is the pattern we want wherever agents work: act freely, leave evidence, and let the rules check it.
What a receipt does not prove
A receipt proves that this commit's own tests reported this result, signed by a job that ran none of the pull request's code. It does not prove the change is correct. A pull request can still weaken its own tests, by deleting them, skipping them or changing what they check, so test changes still need a human review.
The evidence is not secret either. It stays in the CI run, and in a public repository any signed-in GitHub user can download it; it is just no longer pasted into the conversation or posted where it can leak. Run artifacts follow your repository's retention, 90 days by default, while the receipt's fingerprints and signature outlast them.
Try it
attested is free and open source under Apache-2.0.
- Run your tests through it: npx @praxso/attested run -- npx playwright test
- Give your agent the same loop: the MCP server works with Claude Code, Codex and Cursor.
- Require receipts on merge: the README walks through the signing workflow and the required check.
The code, the docs and a 45-second video are at github.com/Praxso/attested. We would love to hear where it helps and where it doesn't: open an issue, or tell us how you show your agents' work today.