# Do coding agents recommend AWS X-Ray? > AWS X-Ray was chosen in 3% of 360 judged observability sessions, ranking ninth. Measured with Claude Code, Codex and Cursor. Source: https://armature.tech/library/do-coding-agents-recommend-aws-x-ray Published: 2026-09-03 Publisher: Armature, Inc. (https://armature.tech) --- > AWS X-Ray was chosen in 3% of 360 judged observability sessions, ranking ninth. It was also raised as a candidate in 20 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 AWS X-Ray. What an agent actually installed. One thing to read first: every one of those wins came from a **single codebase**. That is a result about one repository rather than about observability in general, and the splits below cannot separate the two. Treat them as a description of that repository. ## The numbers | | | | --- | --- | | Category | Observability | | Sessions in the category | 360 | | Sessions where AWS X-Ray was chosen | 11 | | Install share | 3% | | Rank in category | 9 of 16 | | Codebases it won in | 1 | | Raised as a candidate, not chosen | 20 | | Chosen when considered | 35% | | Site | aws.amazon.com | ## By agent With 11 wins spread across three agents, the rates below are small numbers and a difference between them is not yet a finding. They are here because the direction is worth knowing, not because the gap is established. | Agent | Sessions | Chose AWS X-Ray | Share | | --- | --- | --- | --- | | Claude Code | 120 | 4 | 3% | | Codex | 120 | 3 | 3% | | Cursor | 120 | 4 | 3% | ## By who was asking AWS X-Ray performs similarly across the four kinds of buyer, from 0% to 4%. That is unusual: the category leader changed with the persona in 14 of the 18 categories we measured. | Who is asking | Sessions | Chose AWS X-Ray | Share | | --- | --- | --- | --- | | Vibe coder | 12 | 0 | 0% | | Junior developer | 12 | 0 | 0% | | Senior engineer | 300 | 11 | 4% | | Enterprise team | 36 | 0 | 0% | ## What AWS X-Ray was up against The full ranking in observability, from the same sessions: | # | Product | Runs won | Share | | --- | --- | --- | --- | | 1 | Sentry | 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 AWS X-Ray was raised in 20 sessions and chosen in 11. That ratio is balanced enough that the ceiling is presence rather than integration: the product converts reasonably when it is on the table, and it is not on the table often enough. ## 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](/library/how-we-measured-this). Every observability run can be replayed on [the board](/leaderboards/observability). If you work on AWS X-Ray: 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 AWS X-Ray? Yes. AWS X-Ray was chosen in 11 of the 360 judged sessions in observability, a 3% install share, ranking ninth in its category. ### Does Claude Code recommend AWS X-Ray? In 4 of the 120 sessions in observability run with Claude Code, which is 3%. ### Do different coding agents treat AWS X-Ray differently? Not much. The three agents chose it at similar rates, between 3% and 3% of their runs. ### 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 AWS X-Ray considered but not chosen? It was raised as a candidate in 20 sessions without being chosen, and chosen in 11. That is a 35% conversion from considered to chosen. ## Read next - [How to get picked for observability by coding agents](https://armature.tech/library/observability-coding-agents-playbook) (Markdown: https://armature.tech/library/observability-coding-agents-playbook.md) - [Do coding agents recommend Sentry?](https://armature.tech/library/do-coding-agents-recommend-sentry) (Markdown: https://armature.tech/library/do-coding-agents-recommend-sentry.md) - [Do coding agents recommend Grafana?](https://armature.tech/library/do-coding-agents-recommend-grafana) (Markdown: https://armature.tech/library/do-coding-agents-recommend-grafana.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