From the experiment

Do coding agents recommend Aikido Security?

Aikido Security was chosen in 10% of 139 judged security platforms sessions, ranking fourth. Measured with Claude Code, Codex, Grok Build CLI and Muse Code.

Published October 14, 2026 Updated November 13, 2026 Read as Markdown

Aikido Security was chosen in 10% of 139 judged security platforms sessions, ranking fourth. It was also raised as a candidate in 32 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 platforms inside a realistic codebase. Not what a chat assistant says about Aikido Security. What an agent actually chose.

The numbers

CategorySecurity platforms
Sessions in the category139
Sessions where Aikido Security was chosen14
Install share10%
Rank in category4 of 19
Codebases it won in3
Raised as a candidate, not chosen32
Chosen when considered30%
Siteaikido.dev

By agent

With 14 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.

AgentSessionsChose Aikido SecurityShare
Claude Code51816%
Codex3013%
Grok Build CLI30517%
Muse Code2800%

What Aikido Security was up against

The full ranking in security platforms, from the same sessions:

#ProductRuns wonShare
1Checkmarx One4331%
2GitLab Security2820%
3Snyk2216%
4Aikido Security (this page)1410%
5HCL AppScan75%
6GitHub Advanced Security + ZAP54%
7GitHub Advanced Security + Microsoft Defender for Cloud32%
8DefectDojo + Gitleaks + Semgrep + Trivy + ZAP32%

What this means

Aikido Security was raised in 32 sessions and chosen in 14. 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 139 sessions in security platforms are part of a published set of 15,379, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.

Every security platforms run can be replayed on the board.

If you work on Aikido Security: 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 Aikido Security?

Yes. Aikido Security was chosen in 14 of the 139 judged sessions in security platforms, a 10% install share, ranking fourth in its category.

Does Claude Code recommend Aikido Security?

In 8 of the 51 sessions in security platforms run with Claude Code, which is 16%.

Do different coding agents treat Aikido Security differently?

Yes, and by a wide margin. Grok Build CLI chose it in 17% of its runs and Codex in 3%.

How was this measured?

Real coding agents at pinned versions were run in sandboxes inside 110 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 Aikido Security considered but not chosen?

It was raised as a candidate in 32 sessions without being chosen, and chosen in 14. That is a 30% conversion from considered to chosen.

Where this comes from

Armature ran 15,379 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 110 realistic codebases, and published every run. The numbers on this page come from that work.

Read next

All library pages