Do coding agents recommend Sentry?
Sentry is the most chosen observability tool, taking 37% of 360 judged observability sessions. Measured with Claude Code, Codex and Cursor.
Sentry is the most chosen observability tool, taking 37% of 360 judged observability sessions. It was also raised as a candidate in 122 further sessions without being chosen.
This page reports what happened when Claude Code, Codex and Cursor had to solve a problem in observability inside a realistic codebase. Not what a chat assistant says about Sentry. What an agent actually installed.
The numbers
| Category | Observability |
| Sessions in the category | 360 |
| Sessions where Sentry was chosen | 133 |
| Install share | 37% |
| Rank in category | 1 of 16 |
| Codebases it won in | 7 |
| Raised as a candidate, not chosen | 122 |
| Chosen when considered | 52% |
| Site | sentry.io |
By agent
The three agents treat Sentry very differently. Cursor chose it in 50% of its sessions in this category and Codex in 24%, a spread of 26 points.
| Agent | Sessions | Chose Sentry | Share |
|---|---|---|---|
| Claude Code | 120 | 44 | 37% |
| Codex | 120 | 29 | 24% |
| Cursor | 120 | 60 | 50% |
A single blended install share would report the midpoint and hide both ends. If most of your users run Codex, your real position here is 24%, not 37%.
By who was asking
Sentry does much better with one kind of buyer than another. It won 100% of sessions asked as junior developer and 8% of those asked as vibe coder.
| Who is asking | Sessions | Chose Sentry | Share |
|---|---|---|---|
| Vibe coder | 12 | 1 | 8% |
| Junior developer | 12 | 12 | 100% |
| Senior engineer | 300 | 116 | 39% |
| Enterprise team | 36 | 4 | 11% |
What Sentry was up against
The full ranking in observability, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Sentry (this page) | 133 | 37% |
| 2 | Grafana | 52 | 14% |
| 3 | Amazon CloudWatch | 30 | 8% |
| 4 | Built in-house (no product adopted) | 22 | 6% |
| 5 | Checkly | 17 | 5% |
| 6 | Datadog | 16 | 4% |
| 7 | Better Stack | 15 | 4% |
| 8 | New Relic | 15 | 4% |
What this means
Leading a category is a position to defend rather than a result to celebrate. In our data, leaders lose ground in exactly two situations: when the person asking is an enterprise buyer with procurement constraints, and when a competitor's documentation is easier for an agent to integrate correctly.
The defence is unglamorous. Keep the quickstart running. Keep the version current on the page. Keep the names aligned. Stay in the templates.
Where these numbers come from
The 360 sessions in observability are part of a published set of 5,292, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every observability run can be replayed on the board.
If you work on Sentry: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts.
<!-- generated by scripts/write-data-pages.mjs -->
Common questions
Do coding agents recommend Sentry?
Yes. Sentry was chosen in 133 of the 360 judged sessions in observability, a 37% install share, ranking first in its category.
Does Claude Code recommend Sentry?
In 44 of the 120 sessions in observability run with Claude Code, which is 37%.
Do different coding agents treat Sentry differently?
Yes, and by a wide margin. Cursor chose it in 50% of its runs and Codex in 24%.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 51 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind.
How often is Sentry considered but not chosen?
It was raised as a candidate in 122 sessions without being chosen, and chosen in 133. That is a 52% conversion from considered to chosen.
Where this comes from
Armature ran 5,292 judged sessions with Claude Code, Codex and Cursor inside 51 realistic codebases, and published every run. The numbers on this page come from that work.