# Autonomous software maintenance

Bugstack finds what breaks, proves the fix, and opens the pull request.

[Get started](https://dashboard.bugstack.ai/login)[Book a demo](/demo)

We are building toward the end of manual software maintenance. *Spend the time on what you want to make.*

### What Bugstack does on its own today

-   Fixes crashes
-   Fixes failing CI
-   Fixes failed deploys
-   Fixes bugs your customers report
-   Upgrades packages
-   Patches vulnerable packages
-   Finds committed secrets
-   Runs security audits
-   Answers review comments

Verified

## Don't report raw HTML 502 body as error message in sourcemap proxy

bugstackai/bugstack · Error · proposed 2d ago

### Changes 2 files · +1 −1

app/api/ingest/sdk/api/sourcemaps/upload/route.ts+1 −1

8787 if (upstream.status >= 500) {

8888 const upstreamError =

89− (data && typeof data === "object" && "error" in data

89+ (!/^\\s\*</.test(text) && data && typeof data === "object"

9090 ? ((data as { error: string }).error)

9191 : \`Upstream ${upstream.status}\`

9292 reportCaughtError(new Error(upstreamError), {

#### Properties

AgentFixer

AutonomyAutopilot

Pull request#271

#### Activity

-   Detected2d
-   Fix proposed2d
-   PR opened2d
-   Merged2d
-   Held up in production1d

A real fix on Bugstack's own repository: detected, fixed, merged, and still holding in production a day later.

## It finds the work before anyone files a ticket.

Bugstack watches your running app and your repository. When something breaks or goes out of date, it starts on its own.

Your app reports a crash through Bugstack A customer bug report CI fails on GitHub Hosting provider logs Scheduled scans A security audit Bugstackfinds the cause Sandbox✗ test fails on your code✓ passes with the fix Pull requestyour CI runs Merged by you, oron Autopilot

Sentry and Datadog are trademarks of their respective owners. Bugstack is not affiliated with or endorsed by them.

### Coming soon

-   Silent error finding
-   Errors in your users' browsers
-   Performance regressions
-   More hosting providers
-   Repositories outside GitHub

## Every bug fix is proven in a sandbox first.

Bugstack copies your repository into an isolated sandbox and writes a test that reproduces the bug. The test has to fail on your code, then pass with the fix.

Sandbox No network None of your secrets Destroyed afterwards the new test Fails on your code the fix the same test Passes with the fix the rest of your suite 212 of 212 still pass

-   ### The test must fail with the bug's own error
    
    A test that fails for anything else, a typo or a bad import, never counts.
    
-   ### Nothing gets in or out
    
    Dependencies install, then the network is cut before the first test runs. Your secrets never go in.
    
-   ### The pull request includes the test
    
    The proof travels with the fix, and your own CI runs on it too.
    

## You set how much it does alone.

Every rule that can hold a change is a setting you own, for each repository.

acme/storefrontWhat Bugstack does on its owndefaults shown · every setting is per repository

### Autonomy

Suggest Review Autopilot

1.  Writes the fix
2.  Opens the pull request
3.  Merges it

BugstackYou

### Proof before merging

Bugstack's sandbox and your CI Bugstack's sandbox only Your CI only No proof needed

### Bugstack allowed to merge

Sign-in code Security code Major version updates Fixes that change a test Infrastructure changes Rotating a secret

### Bugstack may

Change dependency files Roll back a bad deploy Suggest data rules

Most files in one change

−+

Most lines in one change

−+

Most redos of one fix

−+

## First place on SWT-Bench Verified,  
scored by its maintainers.

SWT-Bench measures whether an agent can write a test that fails on a real bug and passes once the bug is fixed. Writing that test unaided is a cornerstone of autonomous software engineering, and it is the step Bugstack runs before every bug fix.

BugstackSonnet 5.5 writes the test, Opus 5.5 picks it 91.5% Claude Code, Opus 5.5next on the leaderboard 87.8% Claude Code, Sonnet 5.5the same model Bugstack writes with 75.8% ~15.7 points

433 real GitHub issues. Scored by the benchmark's maintainers, 1 Nov 2026. [See the leaderboard at swtbench.com](https://swtbench.com/?results=verified) · [How the run was scored](/swt-bench)

-   ### What it asks of an agent
    
    Each task is a real GitHub issue from an open source Python project. The agent gets the issue and the code, and has to write a test that fails before the fix and passes after it.
    
-   ### Why that matters
    
    An agent that can reproduce a bug on its own can show that its fix worked, with nobody checking by hand. Every proven fix starts with that test.
    
-   ### How Bugstack compares
    
    Bugstack writes its tests with Sonnet 5.5 and uses Opus 5.5 to pick the best one. Claude Code scored 87.8% on Opus 5.5 and 75.8% on Sonnet 5.5.
    

43 of 44

fixes held on an exam of bugs we planted in our own code, sealed before we tuned the fixer.

245 of 252

held on the full set of planted bugs, in TypeScript, Python, Go and Ruby.

## Hand off the upkeep.  
Go build.

$100 a month. Start with a 14-day trial: $50 of credit and a first security audit on us.

[Get started](https://dashboard.bugstack.ai/login)

Or book 15 minutes with the founder

[Open the booking page](/demo)