Debugg AI
Automated browser tests on every pull requestTest results as GitHub comments, zero setup
Highlights
What you can do with it
- Run browser tests automatically on every open-source pull request
- Catch interface regressions before merging new features
- Verify a code change without manual clicking
How to use it
- 1 Register at debugg.ai and log in
- 2 Connect your GitHub repository with one click
- 3 Complete the short setup, about two minutes
- 4 Open a pull request to trigger a test run
- 5 Read the results in the GitHub PR comments
Who it is for
Pros
- No configuration required
- Tests run on every pull request
- Results land where you already work
- Free tier for open-source and public repositories
Limitations
- Free tier is limited to 100 tests per month and public repositories
- Private and commercial work needs a paid plan
- AI-generated tests still need review
- Remote browser testing depends on the service being available
What Debugg AI is
DebuggAI runs automated browser tests on each pull request and posts the results as GitHub comments. There is no configuration to maintain: the service clones your repository, builds the project, opens a remote browser, and walks the application using AI that builds a knowledge graph of pages, interactions, and user flows. Each test reports its purpose, status, and a direct debugging link, so you can see what failed and why. Security is handled with encrypted tunnels, isolated environments, and temporary access. A free version covers open-source projects and public repositories with 100 tests per month, and paid plans serve professional developers and teams.
What you can do with it
- Trigger browser tests automatically on every pull request.
- Read results as comments without leaving GitHub.
- Let AI explore the app and map user flows.
- Jump straight from a failed test to debugging information.
- Keep code checks running without writing them by hand.
Who it is for
- Open-source maintainers reviewing contributions.
- Professional developers shipping web applications.
- Enterprise QA teams that want automated coverage.
What to watch out for
The free tier is limited to 100 tests per month and public repositories, so private and commercial work needs a paid plan. AI-generated tests still deserve review, because they cover what the model understands rather than everything you care about. Remote browser testing also depends on the service being reachable at the moment your pull request lands. Features and interface details may change between versions, so review the latest notes on the page before you start. For team use, agree on naming and editing conventions in advance to avoid version conflicts or duplicated work.
FAQ
Is there a free version?
Yes, the free version suits open-source projects and public repositories with 100 tests per month.
How do results arrive?
As comments on the GitHub pull request.
Do I need to configure anything?
No complex configuration is required; setup takes about two minutes.
Why it is free
What the official page says： free version
Free limits, trial length and features are decided by the official site and can change at any time.
Product preview
Screenshot archived from the listing page, for preview only.
