Everything bugstack does
Everything between error and fix, handled for you
Three lines in your app. That’s the whole integration.
import { ErrorCaptureClient } from 'bugstack-sdk'
ErrorCaptureClient.init({ apiKey: process.env.BUGSTACK_API_KEY })
import bugstack
bugstack.init(api_key=os.environ["BUGSTACK_API_KEY"])
require 'bugstack'
Bugstack.init(api_key: ENV['BUGSTACK_API_KEY'])
import "github.com/MasonBachmann7/bugstack-go"
bugstack.Init(bugstack.Config{APIKey: os.Getenv("BUGSTACK_API_KEY")})
Full setup in the Quickstart.
Surgical AI Fixes
bugstack reads the erroring file, its imports, types, and tests from your repo, then generates minimal, targeted changes. Multi-file fixes supported, syntax and scope validated before commit.
CI-Aware Testing
bugstack waits for your CI pipeline to run against every PR. If CI fails, bugstack gets a second attempt with the failure output as context, then recommits to the same branch.
GitHub-Native
Every fix lands as a real pull request with the error details, stack trace, fix explanation, confidence badge, and changed files. Auto-merge or review manually.
Smart Deduplication
Errors are fingerprinted by type, route, and stack frame. Duplicates within 5 minutes never leave the SDK; duplicates within 24 hours at the server roll up into a single incident with an incremented count — so you see one row per real bug, not a flood.
Per-Project Control
Each project has independent settings: confidence thresholds, auto-fix toggle, and deploy method (manual review or auto-merge).
Claude Under the Hood
bugstack orchestrates Claude across your repo — the moat is the context, pipeline, and guardrails. We build the working set (repo structure, failing test, stack frame, surrounding code), hand it to Claude to author the diff, then validate, test, and gate the output against your CI before it hits a PR.
Sensitive-Data Redaction
API keys, tokens, passwords, and common secret patterns are redacted from error payloads before they leave your runtime. Your credentials never reach our servers, and never reach Claude. Learn more →
Dry-Run Mode
Turn on dry_run and bugstack will generate the fix and the PR description without opening a PR — you review the diff in your dashboard first, then decide whether to ship it.
Multi-Language, One Pipeline
JavaScript, TypeScript, Python, Ruby, and Go SDKs — all feed the same capture, dedup, fix, and PR pipeline. One dashboard, one API key, one billing tier, regardless of stack.
Built with Production-Grade Technology
Built on the same trusted tools you already use
Beyond Error Monitoring
Error monitoring tells you what broke. bugstack fixes it.
Traditional error monitoring tools like Sentry, Datadog, and PagerDuty alert you when something breaks. bugstack works alongside them as the fix layer: it identifies the code path, opens a PR, runs CI, and follows your merge rules.
| Capability | Error Monitoring | bugstack |
|---|---|---|
| Detects production errors | ✓ | ✓ |
| Sends alerts & notifications | ✓ | Dashboard |
| Identifies error source in code | Partial | ✓ |
| Writes a validated fix | ✕ | ✓ |
| Opens a pull request | ✕ | ✓ |
| Runs fix through CI | ✕ | ✓ |
| Auto-merges PRs when CI passes | ✕ | ✓ |
bugstack works alongside your existing monitoring stack. Keep Sentry. Add the fix layer. See the full comparison →
Never Look Back.
Stop triaging. Start shipping.
Start Your Free Trial