From a customer’s bug report to a fix that is live.

A customer tells you something is broken. Bugstack reads the report, reproduces the bug with a failing test, writes the fix, opens the pull request, and tells the customer once the fix is live. You decide how much of that happens without you.

What happens to a report

  1. The report arrives. From your helpdesk, a GitHub issue or the dashboard, in the customer’s own words.
  2. Bugstack sorts it. Each support ticket is read once and marked as a bug, a duplicate, not a bug, or needing more information. Only bugs go further.
  3. The Tester reproduces it. In an isolated sandbox it writes a test from the description. The test has to fail on your current code for the reason the customer described.
  4. The Fixer fixes it. The fix has to make that same test pass while the rest of your suite stays green.
  5. A pull request opens. It carries the test and the fix, and it follows the autonomy level you set for that repository.
  6. The customer hears back. When the fix is live, they get a reply on the ticket they filed.

Where reports come from

SourceHow it connects
ZendeskConnect it on the Connections page. Tickets your customers file become bug reports.
IntercomConnect it on the Connections page. Conversations that report a bug become bug reports.
FreshdeskConnect it on the Connections page. Tickets your customers file become bug reports.
Support emailForward your support inbox to an address Bugstack gives you.
GitHub issuesA member of the repository adds the bugstack label to an open issue.
DashboardAn admin files it with the Report a bug form: a title and a description.

Personal details in a support ticket are redacted before the ticket is stored, and the customer’s contact address is encrypted.

Reproduced before it is fixed

A bug report is a bug described in words. There is no stack trace to read, so the first job is to prove the bug exists. Bugstack’s Tester copies your repository into a sandbox with the network cut, writes a test from the description, and runs it against your default branch. It gets three attempts.

A reproduced report is handled like any crash Bugstack fixes: the Fixer writes the change, and the test that proved the bug has to pass before a pull request opens. How Bugstack proves a fix

If the Tester cannot reproduce the report, Bugstack does not attempt a fix. You choose what happens instead: the report goes back to your support team with a note on what was tried, or Bugstack asks the customer a clarifying question, twice at most.

The customer hears back

On a GitHub issue, Bugstack comments with what it found: reproduced, or could not reproduce.

On a support ticket, the customer gets one message when the bug is fixed. Bugstack sends it once the fix is live, which means deployed and holding in production. A merged pull request alone does not send it.

You stay in control

  • Messages to customers. Off, draft or sent by Bugstack. The default is draft: a person approves each message before it goes out.
  • The fix. A fix that started from a report follows the repository’s autonomy level: Suggest, Review or Autopilot. New repositories start on Review, where you do the merging.
  • Reports it cannot reproduce. Handed back to your team, or followed up with the customer. You pick.

How well it works

Writing a failing test from a description of a bug is the skill SWT-Bench Verified measures. Each of its 433 tasks is a real GitHub issue, and the agent has to write a test that fails before the fix and passes after it. Bugstack’s Tester is first on that leaderboard at 91.5%, scored by the benchmark’s maintainers on 1 November 2026. How the run was scored

We also use it on Bugstack’s own code: bugs we notice in the dashboard are filed through the same form and reproduced the same way.

What it does not do yet

  • A report carries a title and a description. Screenshots and attachments are not read.
  • There is no widget for your own app. Reports come from the sources listed above.
  • Reports do not come in from Slack, Linear or Jira.
  • The repository needs a test suite that runs in Bugstack’s sandbox.

Frequently Asked Questions

Can Bugstack fix a bug a customer reported?

Yes. A report written in plain words, from a support ticket, a GitHub issue or the dashboard, goes to Bugstack’s Tester. It writes a test that fails for the reason the customer described, and the fix has to make that test pass before a pull request opens.

Which support tools does Bugstack connect to?

Zendesk, Intercom and Freshdesk, plus a forwarding address for any support inbox. Reports also come from a GitHub issue labelled Bugstack and from the Report a bug form in the dashboard. Another helpdesk can be connected on request.

What happens when Bugstack cannot reproduce a report?

It does not guess at a fix. You choose what happens next: the report goes back to your support team with a note on what was tried, or Bugstack asks the customer a clarifying question, twice at most.

Does Bugstack message my customers on its own?

Only if you allow it. By default every message to a customer is a draft that a person approves. You can switch customer messages off, or let Bugstack send them itself.

When does the customer hear that the bug is fixed?

Once the fix is live. Bugstack waits until the change is deployed and holding in production. A merged pull request alone does not trigger the message.

See it work on your own code.

$100 a month

Includes $100 of usage credit every month. Start with a 14-day trial: $50 of credit and a first security audit on us. A card is required.