Do coding agents recommend E2B?
E2B is the most chosen code sandbox, taking 44% of 520 judged code sandboxes sessions. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
E2B is the most chosen code sandbox, taking 44% of 520 judged code sandboxes sessions. It was also raised as a candidate in 266 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 code sandboxes inside a realistic codebase. Not what a chat assistant says about E2B. What an agent actually installed.
The numbers
| Category | Code sandboxes |
| Sessions in the category | 520 |
| Sessions where E2B was chosen | 227 |
| Install share | 44% |
| Rank in category | 1 of 7 |
| Codebases it won in | 5 |
| Raised as a candidate, not chosen | 266 |
| Chosen when considered | 46% |
| Site | e2b.dev |
By agent
The agents treat E2B very differently. Muse Code chose it in 80% of its sessions in this category and Codex in 7%, a spread of 73 points.
| Agent | Sessions | Chose E2B | Share |
|---|---|---|---|
| Claude Code | 129 | 51 | 40% |
| Codex | 170 | 12 | 7% |
| Cursor | 136 | 100 | 74% |
| Grok Build CLI | 34 | 23 | 68% |
| Muse Code | 51 | 41 | 80% |
A single blended install share would report the midpoint and hide both ends. If most of your users run Codex, your real position here is 7%, not 44%.
By who was asking
E2B does much better with one kind of buyer than another. It won 48% of sessions asked as senior engineer and 5% of those asked as enterprise team.
| Who is asking | Sessions | Chose E2B | Share |
|---|---|---|---|
| Senior engineer | 464 | 224 | 48% |
| Enterprise team | 56 | 3 | 5% |
What E2B was up against
The full ranking in code sandboxes, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | E2B (this page) | 227 | 44% |
| 2 | Modal | 131 | 25% |
| 3 | Vercel Sandbox | 81 | 16% |
| 4 | Daytona | 73 | 14% |
| 5 | Anthropic Code Execution | 3 | 1% |
| 6 | Runloop Devboxes | 3 | 1% |
| 7 | Cloudflare Workers | 2 | 0% |
What this means
Leading a category is a position to defend rather than a result to celebrate. In our data, leaders lose ground in exactly two situations: when the person asking is an enterprise buyer with procurement constraints, and when a competitor's documentation is easier for an agent to integrate correctly.
The defence is unglamorous. Keep the quickstart running. Keep the version current on the page. Keep the names aligned. Stay in the templates.
Where these numbers come from
The 520 sessions in code sandboxes are part of a published set of 15,287, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every code sandboxes run can be replayed on the board.
If you work on E2B: 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 E2B?
Yes. E2B was chosen in 227 of the 520 judged sessions in code sandboxes, a 44% install share, ranking first in its category.
Does Claude Code recommend E2B?
In 51 of the 129 sessions in code sandboxes run with Claude Code, which is 40%.
Do different coding agents treat E2B differently?
Yes, and by a wide margin. Muse Code chose it in 80% of its runs and Codex in 7%.
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 E2B considered but not chosen?
It was raised as a candidate in 266 sessions without being chosen, and chosen in 227. That is a 46% conversion from considered to chosen.
Where this comes from
Armature ran 15,287 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.