Do coding agents recommend DBOS Transact?
DBOS Transact was chosen in 2% of 681 judged agent frameworks sessions, ranking tenth. Measured with Claude Code, Codex and Cursor.
DBOS Transact was chosen in 2% of 681 judged agent frameworks sessions, ranking tenth. It was also raised as a candidate in 11 further sessions without being chosen.
This page reports what happened when Claude Code, Codex and Cursor had to solve a problem in agent frameworks inside a realistic codebase. Not what a chat assistant says about DBOS Transact. What an agent actually installed.
The numbers
| Category | Agent frameworks |
| Sessions in the category | 681 |
| Sessions where DBOS Transact was chosen | 14 |
| Install share | 2% |
| Rank in category | 10 of 35 |
| Codebases it won in | 3 |
| Raised as a candidate, not chosen | 11 |
| Chosen when considered | 56% |
| Site | dbos.dev |
By agent
With 14 wins spread across 3 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 DBOS Transact | Share |
|---|---|---|---|
| Claude Code | 237 | 8 | 3% |
| Codex | 243 | 2 | 1% |
| Cursor | 201 | 4 | 2% |
By who was asking
DBOS Transact performs similarly across the four kinds of buyer, from 0% to 6%. That is unusual: the category leader changed with the persona in 24 of the 31 categories we measured.
| Who is asking | Sessions | Chose DBOS Transact | Share |
|---|---|---|---|
| Vibe coder | 163 | 0 | 0% |
| Junior developer | 157 | 0 | 0% |
| Senior engineer | 254 | 14 | 6% |
| Enterprise team | 107 | 0 | 0% |
What DBOS Transact was up against
The full ranking in agent frameworks, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Built in-house (no product adopted) | 170 | 25% |
| 2 | Vercel AI SDK | 95 | 14% |
| 3 | Cursor SDK | 94 | 14% |
| 4 | Inngest | 50 | 7% |
| 5 | Temporal | 29 | 4% |
| 6 | Prism | 28 | 4% |
| 7 | OpenAI Agents SDK | 24 | 4% |
| 8 | LangGraph | 23 | 3% |
What this means
Agents almost never raise DBOS Transact without choosing it: 11 sessions raised against 14 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 681 sessions in agent frameworks 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 agent frameworks run can be replayed on the board.
If you work on DBOS Transact: 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 DBOS Transact?
Yes. DBOS Transact was chosen in 14 of the 681 judged sessions in agent frameworks, a 2% install share, ranking tenth in its category.
Does Claude Code recommend DBOS Transact?
In 8 of the 237 sessions in agent frameworks run with Claude Code, which is 3%.
Do different coding agents treat DBOS Transact differently?
Not much. Claude Code, Codex and Cursor chose it at similar rates, between 1% and 3% of their runs.
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 DBOS Transact considered but not chosen?
It was raised as a candidate in 11 sessions without being chosen, and chosen in 14. That is a 56% 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.