From the experiment

Do coding agents recommend Orb?

Orb was chosen in 16% of 548 judged usage-based billing sessions, ranking second. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.

Published September 28, 2026 Updated September 29, 2026 Read as Markdown

Orb was chosen in 16% of 548 judged usage-based billing sessions, ranking second. It was also raised as a candidate in 389 further sessions without being chosen.

This page reports what happened when Claude Code, Codex, Cursor, Grok Build CLI and Muse Code had to solve a problem in usage-based billing inside a realistic codebase. Not what a chat assistant says about Orb. What an agent actually installed.

The numbers

CategoryUsage-based billing
Sessions in the category548
Sessions where Orb was chosen88
Install share16%
Rank in category2 of 16
Codebases it won in10
Raised as a candidate, not chosen389
Chosen when considered18%
Sitewithorb.com

By agent

Claude Code, Codex, Cursor and Muse Code land within 9 points of each other on Orb, which is closer than most products in this experiment manage. Grok Build CLI ran fewer than 30 sessions here, too few to compare.

AgentSessionsChose OrbShare
Claude Code1272620%
Codex1643119%
Cursor1321511%
Grok Build CLI2614%
Muse Code991515%

By who was asking

Orb does much better with one kind of buyer than another. It won 28% of sessions asked as junior developer and 13% of those asked as enterprise team.

Who is askingSessionsChose OrbShare
Junior developer1002828%
Senior engineer2022814%
Enterprise team2463213%

What Orb was up against

The full ranking in usage-based billing, from the same sessions:

#ProductRuns wonShare
1Metronome22541%
2Built in-house (no product adopted)10720%
3Orb (this page)8816%
4Lago6211%
5Stripe Billing132%
6CGRateS132%
7OpenMeter92%
8Oracle BRM71%

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 548 sessions in usage-based billing are part of a published set of 15,051, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.

Every usage-based billing run can be replayed on the board.

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

Yes. Orb was chosen in 88 of the 548 judged sessions in usage-based billing, a 16% install share, ranking second in its category.

Does Claude Code recommend Orb?

In 26 of the 127 sessions in usage-based billing run with Claude Code, which is 20%.

Do different coding agents treat Orb differently?

Not much. Claude Code, Codex, Cursor and Muse Code chose it at similar rates, between 11% and 20% 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 Orb considered but not chosen?

It was raised as a candidate in 389 sessions without being chosen, and chosen in 88. That is a 18% conversion from considered to chosen.

Where this comes from

Armature ran 15,051 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.

Read next

All library pages