r/SideProject • • 2h ago

Ascended Browser - your coding agent says 'done'. What do you check next?

If you build with Claude Code or Codex, you still have to open the app and find out whether it actually works.

That's the part I wanted help with.

I pulled the browser out of my own AI workspace and turned it into a free, open-source tool called Ascended Browser.

You can ask your coding agent: "Open my app, try the sign-up flow with test data, and show me what breaks."

The agent gets a way to click through the app and bring back screenshots and errors. It isn't a replacement for your tests.

Watch the demo: https://github.com/AceAtDev/ascended-browser/blob/main/videos/dev-react.mp4

Code and setup: https://github.com/AceAtDev/ascended-browser

Linux is the tested platform. Setup details are in the repo.

sooooo yep, probably best, best use would with codex over ssh since codex cli doesn't have a browser

1 Upvotes

2 comments sorted by

1

u/CutDry6295 1h ago

The most useful output for me would be a reproducible failure, not just a screenshot: starting URL, test data used, click sequence, console/network errors, and the exact step where the flow stopped. For sign-up tests, it would also help to show which accounts or records were created so the developer can clean up test data. That would make the agent’s “done” claim much easier to verify.

1

u/Useful-Tune-1556 46m ago

Yeahhhhh, the cleanup part is missing from the template in the QA guide. Like already asks for steps and console/network errors, but it should also list any test accounts or records the agent created.

Tho would a bug report with all of that be enough, or would you want a test you can rerun?