# Do coding agents recommend Resolve AI? > Resolve AI was chosen in 20% of 179 judged ai sre sessions, ranking second. Measured with Claude Code, Codex and Cursor. Source: https://armature.tech/library/do-coding-agents-recommend-resolve-ai Published: 2026-09-15 Publisher: Armature, Inc. (https://armature.tech) --- > Resolve AI was chosen in 20% of 179 judged ai sre sessions, ranking second. It was also raised as a candidate in 77 further sessions without being chosen. This page reports what happened when Claude Code, Codex and Cursor had to solve a problem in ai sre inside a realistic codebase. Not what a chat assistant says about Resolve AI. What an agent actually installed. ## The numbers | | | | --- | --- | | Category | Ai sre | | Sessions in the category | 179 | | Sessions where Resolve AI was chosen | 35 | | Install share | 20% | | Rank in category | 2 of 26 | | Codebases it won in | 4 | | Raised as a candidate, not chosen | 77 | | Chosen when considered | 31% | | Site | resolve.ai | ## By agent The three agents treat Resolve AI very differently. Codex chose it in 35% of its sessions in this category and Cursor in 8%, a spread of 27 points. | Agent | Sessions | Chose Resolve AI | Share | | --- | --- | --- | --- | | Claude Code | 71 | 7 | 10% | | Codex | 72 | 25 | 35% | | Cursor | 36 | 3 | 8% | A single blended install share would report the midpoint and hide both ends. If most of your users run Cursor, your real position here is 8%, not 20%. ## By who was asking Resolve AI does much better with one kind of buyer than another. It won 63% of sessions asked as senior engineer and 0% of those asked as vibe coder. | Who is asking | Sessions | Chose Resolve AI | Share | | --- | --- | --- | --- | | Vibe coder | 30 | 0 | 0% | | Junior developer | 60 | 5 | 8% | | Senior engineer | 30 | 19 | 63% | | Enterprise team | 59 | 11 | 19% | ## What Resolve AI was up against The full ranking in ai sre, from the same sessions: | # | Product | Runs won | Share | | --- | --- | --- | --- | | 1 | Sentry Seer | 47 | 26% | | 2 | Resolve AI **(this page)** | 35 | 20% | | 3 | Datadog Bits AI Dev Agent + Datadog Bits Investigation | 26 | 15% | | 4 | Cursor Automations | 15 | 8% | | 5 | Claude Code GitHub Action | 11 | 6% | | 6 | Cursor Cloud Agents | 9 | 5% | | 7 | incident.io AI SRE | 4 | 2% | | 8 | Cursor Automations + Cursor Cloud Agents | 3 | 2% | ## What this means A solid second or third position in a category means the agent is genuinely choosing rather than reaching automatically. That is a winnable position, because the inputs it uses can be changed. The fastest gains are usually in the sessions that were nearly won: read them, find the step where the agent moved on, and fix that step. ## Where these numbers come from The 179 sessions in ai sre are part of a published set of 7,852, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: [how we measured this](/library/how-we-measured-this). Every ai sre run can be replayed on [the board](/leaderboards/ai-sre). If you work on Resolve AI: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts. ## Common questions ### Do coding agents recommend Resolve AI? Yes. Resolve AI was chosen in 35 of the 179 judged sessions in ai sre, a 20% install share, ranking second in its category. ### Does Claude Code recommend Resolve AI? In 7 of the 71 sessions in ai sre run with Claude Code, which is 10%. ### Do different coding agents treat Resolve AI differently? Yes, and by a wide margin. Codex chose it in 35% of its runs and Cursor in 8%. ### How was this measured? Real coding agents at pinned versions were run in sandboxes inside 90 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 Resolve AI considered but not chosen? It was raised as a candidate in 77 sessions without being chosen, and chosen in 35. That is a 31% conversion from considered to chosen. ## Read next - [How to get picked for ai sre by coding agents](https://armature.tech/library/ai-sre-coding-agents-playbook) (Markdown: https://armature.tech/library/ai-sre-coding-agents-playbook.md) - [Do coding agents recommend Sentry Seer?](https://armature.tech/library/do-coding-agents-recommend-sentry-seer) (Markdown: https://armature.tech/library/do-coding-agents-recommend-sentry-seer.md) - [Do Claude Code, Codex and Cursor pick the same tools?](https://armature.tech/library/do-claude-code-and-codex-agree) (Markdown: https://armature.tech/library/do-claude-code-and-codex-agree.md) --- Armature helps software products get discovered and used by coding agents. Service: https://armature.tech/discoverability · Results: https://armature.tech/leaderboards/sectors · Contact: contact@armature.tech