proofshot / codex
AGENTS.md866 starsChanged 9 months agoMITView on GitHub
ProofShot is an open-source, agent-agnostic CLI that lets any AI coding agent verify its own work in a real browser — no vendor lock-in required. After building or modifying UI features, verify with this workflow: 1. Start: proofshot start --run "your-dev-command" --port PORT --description "what you are verifying" If the server is already running, omit --run. 2. Test: Use proofshot exec to navigate, click, fill forms, take screenshots 3. Stop: proofshot stop — bundles video, screenshots, and error report Key…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 5
After building or modifying UI features, verify with this workflow:
- Very specific: line 8
If the server is already running, omit --run.
- Very specific: line 9
Test: Use proofshot exec to navigate, click, fill forms, take screenshots
- Very specific: line 10
Stop: proofshot stop — bundles video, screenshots, and error report
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ProofShot Visual Verification
ProofShot is an open-source, agent-agnostic CLI that lets any AI coding agent verify its own work in a real browser — no vendor lock-in required.
After building or modifying UI features, verify with this workflow:
- Start:
proofshot start --run "your-dev-command" --port PORT --description "what you are verifying"If the server is already running, omit --run. - Test: Use
proofshot execto navigate, click, fill forms, take screenshots - Stop:
proofshot stop— bundles video, screenshots, and error report
Key proofshot exec commands:
proofshot exec snapshot -i— see interactive elementsproofshot exec click @e3— click an elementproofshot exec fill @e2 "text"— fill a form fieldproofshot exec screenshot step.png— capture a moment
Artifacts saved to ./proofshot-artifacts/ including video, screenshots, errors, and summary.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.