Do coding agents recommend Strix?
Strix was chosen in 2% of 460 judged security testing sessions, ranking eighth. Measured with Claude Code, Codex, Grok Build CLI and Muse Code.
Strix was chosen in 2% of 460 judged security testing sessions, ranking eighth. It was also raised as a candidate in 3 further sessions without being chosen.
This page reports what happened when Claude Code, Codex, Grok Build CLI and Muse Code had to solve a problem in security testing inside a realistic codebase. Not what a chat assistant says about Strix. What an agent actually installed.
The numbers
| Category | Security testing |
| Sessions in the category | 460 |
| Sessions where Strix was chosen | 11 |
| Install share | 2% |
| Rank in category | 8 of 65 |
| Codebases it won in | 4 |
| Raised as a candidate, not chosen | 3 |
| Chosen when considered | 79% |
| Site | usestrix.com |
By agent
With 11 wins spread across 4 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 Strix | Share |
|---|---|---|---|
| Claude Code | 116 | 3 | 3% |
| Codex | 116 | 7 | 6% |
| Grok Build CLI | 116 | 1 | 1% |
| Muse Code | 112 | 0 | 0% |
What Strix was up against
The full ranking in security testing, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | ZAP | 111 | 24% |
| 2 | Semgrep | 78 | 17% |
| 3 | SonarQube | 66 | 14% |
| 4 | Burp Suite | 30 | 7% |
| 5 | GitHub Advanced Security | 25 | 5% |
| 6 | Trivy | 14 | 3% |
| 7 | StackHawk | 12 | 3% |
| 8 | Strix (this page) | 11 | 2% |
What this means
Agents almost never raise Strix without choosing it: 3 sessions raised against 11 chosen. When it gets considered, it usually wins. The constraint is how rarely it gets considered at all, which is a presence problem: templates, framework integrations and pages that answer the configuration and production questions agents actually search for.
Where these numbers come from
The 460 sessions in security testing are part of a published set of 15,000, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every security testing run can be replayed on the board.
If you work on Strix: 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 Strix?
Yes. Strix was chosen in 11 of the 460 judged sessions in security testing, a 2% install share, ranking eighth in its category.
Does Claude Code recommend Strix?
In 3 of the 116 sessions in security testing run with Claude Code, which is 3%.
Do different coding agents treat Strix differently?
Not much. Claude Code, Codex, Grok Build CLI and Muse Code chose it at similar rates, between 0% and 6% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 92 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 Strix considered but not chosen?
It was raised as a candidate in 3 sessions without being chosen, and chosen in 11. That is a 79% conversion from considered to chosen.
Where this comes from
Armature ran 15,000 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 92 realistic codebases, and published every run. The numbers on this page come from that work.