AI debug engineer
An AI debug engineer finds why a customer got stuck and opens the pull request. You review it.
Card required. 3 days before you are billed.
Read-only. Opens a pull request. Never merges.
Nothing open yet.
Works with the stack you already run
One SDK for the browser, one for the server. Same visit.
The message does not say who, or which line. Finding that out takes hours. Then you still write the fix.
01
An error. No name on it.
02
What they clicked is in another tool.
03
The file you have open may not be the one that failed.
04
After all that, you still write it yourself.
Without Bugwalk
With Bugwalk
An AI debug engineer does those hours. You review the pull request.
Drag to compare.
With Bugwalk
Without Bugwalk
Their visit, the reason, and a pull request you review. The numbers are what a plan includes.
01
2h
About two hours back, minus the time it took to open the request.
02
100
A month on Pro. 1,000 on Team.
03
5
A month on Pro. 20 on Team.
04
$39
Team is $149, about forty hours. You still merge.
Bugwalk does not push to the default branch, comment, or merge.
Three real-looking support messages from a small shop. Choose one, press the button, and watch the agent read the code.
Choose a ticket, then press the button.
Nothing open yet.
An AI debug engineer read what they did, named the line that was live, and opened the pull request.
Read the visit
What they did, and where it failed.
Fix the code
The line that failed, and nothing else.
Open the pull request
The request is ready before you debug.
You review it
You decide when it merges.
fernhill/checkout
src/checkout/total.ts
- return subtotal * (1 - discount.percentage / 100);+ if (!discount) return subtotal;+ return subtotal * (1 - discount.percentage / 100);
About two hours, looking it up by hand
5 places
Logs · Requests · What they did · GitHub · The live version
Reviewing the one request
Five places to check, then one request to review.
Five links, kept together on one visit. Break any one and you are back in five tabs.
The email they sent you opens their visits.
Every click, in order, on one timeline.
The request and the error, on the same visit.
The release that was live, not the file on your screen.
A pull request written against that version.
What they clicked, what the app did, and the error stay on one visit.
01
The click and the request stay together.
02
The error stays on that same visit.
03
When they say it broke, you open their visit.
Every reason points at something that happened, or at a line in your code. If the proof is thin, the report says so.
See who hit it, what they did, and why. Fix it once.
Move the sliders. The only number we supply is two hours per small fix.
Pro opens 5 pull requests a month and Team opens 20. Past the plan, you keep the investigations and write the fix yourself.
Hours back a month
10h
Worth of time back
$800
Pro, per project costs $39. About $761 a month ahead after the plan.
Fernhill is a small shop we run. People sign in, check out and sometimes hit a bug. Open its dashboard and read a failure, no account needed.
Read-only. Investigations and pull requests are for your own project.
The last day: who showed up, what failed, and which visits just ended.
Search the email or id you already have, then open someone and read their visits.
One visit: the pages, what they did, what your app did, and where it failed.
The same failure, grouped: who hit it, what they did, and why.
A written answer: what happened, why, how sure it is, and what to change.
How Bugwalk is connected to your product, what it may read, and your plan.
Connect your app and the code it runs, then watch the next failure on the version that was live.
React, frontend:
npx @bugwalk/wizardPoint your existing OpenTelemetry agent at the Bugwalk OTLP endpoint. No Bugwalk library goes into those services at all.
OTEL_EXPORTER_OTLP_ENDPOINT=https://api.bugwalk.appIt can read the failure and open a pull request. It cannot merge, or change your database.
Passwords, card numbers, and API keys are removed before anything is sent. You cannot turn that off.
It can open a pull request. It cannot push to your main branch, comment, or merge.
No. It can open a pull request on a new branch that starts with bugwalk/fix-. It cannot push to your default branch, comment, merge, or write to your database.
The visit that failed and the repositories you choose, at the commit that was live. Passwords, card numbers and keys are removed in your app before anything is sent.
The report says so. A finding that cites nothing it actually saw drops the whole report to low confidence, with the reason shown.
Per project. Pro is $39 a month, Team is $149. Usage stops at the plan limit and is never billed extra.
Yes. The server and SDKs are Apache 2.0. The hosted product adds accounts, the agent and pull requests.
Open source, and hosted if you’d rather not run it. Read how to self-host.
Review the pull request.
Card required. 3 days before you are billed.