BugProof

• 

  It presents a complete chain of evidence for the fix, failed tests, passed tests, and review results.

Inspiration

A screenshot can make a bug obvious to a human, but it rarely provides enough evidence for a coding agent to repair the issue safely. We wanted to replace “AI-generated patch” with a workflow that requires proof.

What it does

BugProof is a local-first developer tool for proof-first software repair.

The prototype guides a bug report through a visible evidence chain:

1. Inspect the visual report and issue context
2. Reproduce the issue at the target viewport
3. Create a failing regression test
4. Apply the smallest safe patch in an isolated workspace
5. Verify the result and record a focused review

Instead of asking developers to trust a plausible patch, BugProof is designed to leave behind proof that the bug existed, that the repair works, and that the change is narrow.

How we built it

The current prototype is built with React, Vite, JavaScript, and CSS. Codex was used throughout the product design and implementation process.

The user experience is complete and deterministic for demos. We are now connecting the execution layer so that local Codex, Playwright, and Git worktree results replace the prototype fixtures.

Challenges we ran into

The central challenge is reliability. A patch can look correct while silently breaking another flow, so we designed the product around reproducibility and verification rather than code generation alone.

Built With

• css
• developer-tools
• javascript
• openai-codex
• react
• vite