The error tracker your agent works in.
Point an unmodified Sentry SDK at Thermite and errors group into issues in your Postgres. Over MCP, a coding agent claims each new issue, reads the same stack trace you see, and leaves its diagnosis on the issue page.
From crash to diagnosis
Thermite never calls a model. It hands the work to your own coding agent — leased, so two agents never triage the same bug twice.
An exception lands
Any Sentry SDK reports it. Grouping folds an error storm into one issue and queues exactly one unit of triage work — in the same transaction, so nothing slips through.
Your agent claims it
Over MCP it gets the exception chain, every stack frame, breadcrumbs — and the release that crashed, so it diagnoses against the revision that actually broke.
The diagnosis comes back
Root cause and suggested fix land on the issue page, next to the alert that told you. You read the answer, not the stack trace.
Triage over MCP
An MCP server serves issues, stack traces and tags to coding agents, which write their findings back onto the issue.
Drop-in for Sentry SDKs
Point your existing DSN at Thermite. Same envelope and store endpoints, same SDKs, no code change.
Grouping that holds
Fingerprints normalize ids, IPs and durations, so one bug stays one issue instead of a thousand.
Alerts per project
Email and webhook routing, per project. Delivery is at-least-once from an outbox, so no alert is dropped in silence.
Cron monitoring
Jobs check in on their schedule. A missed or overrunning run becomes an ordinary error event, grouped and alerted like any other.
Release health
Crash-free rate per release, counted from SDK sessions, so a busy release does not read as a broken one.