Do coding agents recommend Claude Code GitHub Action?
Claude Code GitHub Action was chosen in 6% of 179 judged ai sre sessions, ranking fifth. Measured with Claude Code, Codex and Cursor.
Claude Code GitHub Action was chosen in 6% of 179 judged ai sre sessions, ranking fifth. It was also raised as a candidate in 25 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 Claude Code GitHub Action. What an agent actually installed.
The numbers
| Category | Ai sre |
| Sessions in the category | 179 |
| Sessions where Claude Code GitHub Action was chosen | 11 |
| Install share | 6% |
| Rank in category | 5 of 26 |
| Codebases it won in | 2 |
| Raised as a candidate, not chosen | 25 |
| Chosen when considered | 31% |
| Site | claude.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 Claude Code GitHub Action | Share |
|---|---|---|---|
| Claude Code | 71 | 11 | 15% |
| Codex | 72 | 0 | 0% |
| Cursor | 36 | 0 | 0% |
By who was asking
Claude Code GitHub Action does much better with one kind of buyer than another. It won 18% of sessions asked as junior developer and 0% of those asked as enterprise team.
| Who is asking | Sessions | Chose Claude Code GitHub Action | Share |
|---|---|---|---|
| Vibe coder | 30 | 0 | 0% |
| Junior developer | 60 | 11 | 18% |
| Senior engineer | 30 | 0 | 0% |
| Enterprise team | 59 | 0 | 0% |
What Claude Code GitHub Action 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 | 35 | 20% |
| 3 | Datadog Bits AI Dev Agent + Datadog Bits Investigation | 26 | 15% |
| 4 | Cursor Automations | 15 | 8% |
| 5 | Claude Code GitHub Action (this page) | 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
Claude Code GitHub Action was raised in 25 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 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.
Every ai sre run can be replayed on the board.
If you work on Claude Code GitHub Action: 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 Claude Code GitHub Action?
Yes. Claude Code GitHub Action was chosen in 11 of the 179 judged sessions in ai sre, a 6% install share, ranking fifth in its category.
Does Claude Code recommend Claude Code GitHub Action?
In 11 of the 71 sessions in ai sre run with Claude Code, which is 15%.
Do different coding agents treat Claude Code GitHub Action differently?
Yes, and by a wide margin. Claude Code chose it in 15% of its runs and Codex in 0%.
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 Claude Code GitHub Action considered but not chosen?
It was raised as a candidate in 25 sessions without being chosen, and chosen in 11. That is a 31% conversion from considered to chosen.
Where this comes from
Armature ran 7,852 judged sessions with Claude Code, Codex and Cursor inside 90 realistic codebases, and published every run. The numbers on this page come from that work.