Agentic AI · Pre-launch · Joining the waitlist
For dev teams shipping web apps. buggerd is an agentic AI debugger that auto-detects the console errors, failed renders, and crashes your users hit in production — and turns each one into a reviewed pull request, so engineers stop spending Mondays triaging Sentry tickets.
Thanks — we'll email you when buggerd is ready.
Waitlist members: $5/month base fee waived during the trial. You only pay per merged fix.
Your real users find the bugs. buggerd turns them into reviewable pull requests automatically.
A console error fires. A component fails to render. A click takes seconds when it shouldn't. buggerd's lightweight script captures the failure, what the user was trying to do, and the state at the moment it broke.
It maps the minified error to your source via your source maps, identifies the failing code, and lands a candidate fix on a draft pull request.
Your existing CI runs the fix with your existing secrets. If it passes, the PR is ready. Review, merge, ship.
Compounding signal
The longer buggerd runs, the more of your production error surface is covered. Auto-captured errors and user reports feed the same fix pipeline — and if a regression resurfaces, buggerd catches it again.
Manual reports
Not every bug throws a console error. A button does the wrong thing silently. A feature feels slow. A workflow makes no sense. Drop the buggerd feedback widget on your site — your users tap, type what's broken, and submit. The report flows into the same fix pipeline as auto-captured errors.
Included in every plan. No separate add-on fee.
A few examples
Themable via JS config. Or hand us your design tokens and we'll match.
Anything where buggerd doesn't have the information a human teammate would.
buggerd fixes what's specified. It doesn't guess at what's intended.
No per-seat fees. Hard monthly cap, no overages.
+ per-fix usage on top. Healthy site? You pay $5.
Waitlist offer: $5/month base waived during the trial. You only pay for fixes you actually merge.
The questions developers actually ask before signing up.
Three guardrails, before merge — not after. Every fix is a draft PR, never auto-merged unless you explicitly opt in. Your own CI must pass on the fix branch before the PR is mergeable. And buggerd's GitHub App is scoped to opening PRs only — no admin, no Actions writes, no way to push directly to your default branch. The worst case is a closed PR. Your tests, your secrets, your call.
The interesting 20%:
When buggerd hits one of these, it tells you and stops — it doesn't guess.
No. Every fix lands as a pull request, never a direct push. You review and merge it the same way you would a human contributor's code. If you don't merge it, nothing changes in production.
Drop the buggerd feedback widget on your site. It's a small in-page button — fully brandable to match your design — that opens a form your users can use to report bugs the AI didn't auto-catch: features that feel slow, buttons that do the wrong thing silently, workflows that don't make sense.
Submitted reports flow into the same fix pipeline as auto-captured errors. You can customize:
Included in every plan.
No. buggerd handles the boring 80% — flaky tests, dependency churn, lint noise, copy-paste bugs — so your developers spend their time on the interesting 20%: architecture, product, and the bugs that actually require judgment. Teams using buggerd don't shrink; they ship more.
No. Your code is not used to train our models or any third-party model. We're moving to Anthropic's zero-retention enterprise terms; until that contract is in place, default Anthropic API terms apply today (Anthropic does not train on API traffic). Code submitted during a debug session is deleted within 30 days regardless.
Only what's needed to diagnose the bug: the error message, the stack trace, the URL, the browser, and a small breadcrumb trail of the user's last few actions (clicks, page navigations).
It does not capture form input values, keystrokes, page screenshots, network response bodies, or any element you mark data-buggerd-private. PII scrubbing rules are configurable per project. We are not a session-replay tool.
buggerd uses a minimum-privilege GitHub App scoped to exactly four permissions: contents:write and pull_requests:write (so it can open and update PRs), metadata:read and checks:read (so it can read your CI status). It has no actions:write, no admin permissions, and no credentials to your database, environment variables, third-party APIs, or production runtime. The only write actions are pushing the fix branch and opening or updating a PR.
It uses your existing CI. buggerd opens a draft pull request with a candidate fix; your GitHub Actions runs the same tests, with the same secrets, in the same environment it always has. buggerd reads the result and iterates if needed.
Yes. Auto-merge is an opt-in mode you turn on per project. If your CI passes, the fix ships — no review step. Your tests are the safety net.
It is off by default and we don't recommend it for apps with real customers in them. But for side projects, internal tools, and “I just want this thing to keep working” sites, it's there for the lazy use case it was built for.
You can also flip the opposite direction and turn on Hardened mode — same fix loop plus an automated security review (dependency scan, secret detection, taint analysis, security-tuned LLM reading the diff) before the PR opens. The default is the middle.
No. Every project has a hard spend cap. When it's reached, buggerd pauses and emails you. There is no overage charge and no way to disable the cap from inside the product.
The fixes buggerd generates are normal git commits in your normal repo. There is no lock-in. If we disappear tomorrow, your codebase keeps working exactly as it did before.
Yes. buggerd uses your source maps to translate minified stack traces back into actual code in your repo. You can either upload them on each deploy (we provide a CLI) or host them privately and grant buggerd read access. Without source maps, the AI can't locate the failing code — so this is a hard requirement.
US only — EU on roadmap. Code does not leave that region. On-prem and self-host are not yet supported.
No. The buggerd snippet loads asynchronously and only runs work when an error fires — there is no continuous background activity. Bundle size and load impact are published targets in our docs and we treat regressions on either as P0 bugs.
They tell you. buggerd fixes it.
Those tools capture the same browser errors and surface them in a dashboard. Then it's on your team to triage, reproduce, prioritize, and ship a fix — typically days or weeks later. buggerd does the triage, the diagnosis, and writes the fix as a PR automatically. The dashboard becomes optional.
If you already use Sentry, keep it. We don't replace your observability stack — we replace the triage queue downstream of it. Sentry integration is on the roadmap so you don't have to install two scripts.
A chat model reads code and writes plausible-looking patches. buggerd starts from the real error your real user hit, and only opens a PR after your CI verifies the fix demonstrably passes. The PR includes the test that proves it.
Didn't see your question?
Join the waitlist. Get the $5/month base fee waived during the trial.