The interesting question is not whether a language model can write a patch. It obviously can. The question is what has to be true around the model for that patch to be worth reviewing.
What the agent needs to see
A stack trace tells you where a program died. It rarely tells you why. Consider a TypeError: Cannot read properties of undefined on session.user.id. The trace points at the property access. The cause is thirty milliseconds earlier, in a token refresh that invalidated the session while a concurrent request was mid-read.
No amount of model quality recovers that from the trace alone. What recovers it is the context bundle: the frames, the source around them, the breadcrumbs from before the throw, and the commits that recently touched those lines. Assemble that once, hand it over, and a race condition becomes legible instead of looking like a random null.
Why the plan comes before the patch
A good agent states a root cause in one sentence, then proposes a change plan, then writes code. Those are separate steps for a practical reason: correcting a wrong plan costs a sentence, and correcting a wrong diff costs a review.
If a tool shows you only the diff, it has hidden the step where you could most cheaply have disagreed with it.
Confidence gating
Every step of a run should emit a confidence score, and the run should stop when that score falls below the project's threshold.
This is unglamorous and it is the whole ballgame. A model asked to produce a patch will always produce a patch. The value is in the runs that do not produce one — the ones that pause and say the root cause is not clear enough to proceed. An agent with no gate is a machine for generating confident, plausible, wrong diffs, and reviewing those is more work than fixing the bug yourself.
Parsemend scores fixability before a run starts, and confidence at every step within it. A run that does not start is the system working.
The landscape in 2026
Sentry Seer analyses issues in Sentry's cloud and can open pull requests through a GitHub or GitLab app. As of July 2026 it costs $40 per active contributor per month. Sentry does not document a way to choose the model or supply your own API key.
General coding agents — Claude Code, Codex, Cursor and the rest — will happily fix a bug if you paste the trace in. What they lack is triage: they do not know which of your four thousand open issues is worth a run, and they do not have the breadcrumbs.
Parsemend sits between the two. It triages errors into a fix queue, assembles the context bundle, and then lets you decide where the run executes: on your own servers, from your laptop via npx parsemend fix, orchestrated by us against your API key, or fully managed. In three of those four, your source code never reaches our infrastructure. See the four fix modes.
What none of them do yet
They do not run your tests. Almost no production agent today executes your test suite against its own patch in a sandbox. They reason about the code; they do not verify it. That is why the output must be a draft pull request and why a human still merges.
Parsemend does not do this either. Sandboxed fix validation is the next item on our roadmap, and until it ships we would rather say plainly that the agent is reasoning, not verifying.
Any vendor telling you their agent autonomously fixes production bugs is describing a review queue they have hidden from you, or a liability they have not met yet.