bugzero

Documentation

Getting started

bugzero turns production errors into reviewed fixes: it watches Sentry, and when something breaks, an AI agent opens a GitHub pull request with a fix. Here's everything you need to set up — and why each step matters. The whole thing takes about five minutes.

1. Detect

A new error in a Sentry project you watch triggers a run.

2. Fix

The agent reads the stacktrace, explores your repo, and writes a minimal fix.

3. Review

A pull request appears for you to review and merge — nothing ships automatically.

Setup at a glance

  1. 1Create your account
  2. 2Connect GitHub
  3. 3Connect Sentry
  4. 4Map each project to a repository
  5. 5Limit to the right environments· optional
  6. 6Tune the AI· optional
  7. 7Pick a plan when you're ready· optional
  8. 8Get your first fix· optional

Required setup

1

Create your account

Required

Sign up with your email and a password. You'll get a team workspace and a free trial — 3 runs, no card required.

Why: Everything in bugzero is scoped to a team, so you can invite colleagues later and share integrations and billing. The trial lets you see a real fix before you pay anything.

Create your account
2

Connect GitHub

Required

On the Integrations page, install the bugzero GitHub App, choose the account or organization, and select the repositories the agent is allowed to touch.

Why: The agent needs to read your code to find the root cause and to open pull requests. It connects through a GitHub App with fine-grained, per-repository permissions you control — and it only ever opens PRs. Nothing is merged or deployed automatically.

Open Integrations
3

Connect Sentry

Required

Back on Integrations, connect your Sentry organization via OAuth, then pick the Sentry projects you want bugzero to watch.

Why: New Sentry issues are the trigger for everything bugzero does. OAuth means there's no manual webhook or signing secret to configure, and choosing projects keeps bugzero scoped to the services you actually care about.

Open Integrations
4

Map each project to a repository

Required

For every Sentry project you watch, choose the GitHub repository the agent should fix. You set this right next to each project on the Integrations page.

Why: This is the link that makes the whole pipeline work. bugzero has to know which codebase belongs to which Sentry project — without a mapping, errors come in but no pull requests go out. It's the most commonly missed step.

Open Integrations

Optional, but recommended

5

Limit to the right environments

Optional

On each project mapping, tick the environments to react to — for example production only. Leave them all unticked to watch every environment.

Why: You usually don't want fixes for local, dev, or staging noise. Restricting to production keeps runs focused on real, user-facing bugs and avoids burning your monthly run limit on errors that don't matter.

Open Integrations
6

Tune the AI

Optional

In Settings you can add custom instructions, pick a model, or enable BYOK by saving your own Anthropic API key.

Why: Custom instructions make fixes follow your conventions (“always add a test”, naming rules, etc.). With BYOK you pay Anthropic directly — and in return get a lower bugzero price and much higher run limits. Model selection unlocks once a key is saved.

Open Settings
7

Pick a plan when you're ready

Optional

The trial includes 3 runs. Upgrade any time from Billing, and manage or cancel through the customer portal.

Why: Your plan sets how many runs you get each month and week. Only successful runs and completed dry runs count toward your limits — failed runs are never charged against you.

Open Billing
8

Get your first fix

Optional

When a new error hits a watched project and environment, bugzero opens a run and — unless it's a dry run — a pull request. Track progress on the Runs page, then open the PR, read the diff and root-cause summary, and merge if it's right.

Why: This is the payoff, and it stays under your control: every fix is a reviewable pull request. Use dry-run mode for analysis-only output until you trust the agent.

View Runs

Set everything up but no pull requests?

Almost always one of these:

  • No project → repo mapping yet (step 4) — the single most common cause.
  • The error's environment isn't in your watched list (step 5).
  • No new error has occurred yet — bugzero reacts to new issues, not historical ones.
  • Your run limit is reached or the trial is used up — check Billing.
  • The repository isn't selected in the GitHub card (step 2).

Ready to set up?

Create your account and connect your first repository — it's free to try.

Start free — 3 runsGo to Integrations