Do coding agents recommend Trigger.dev?
Coding agents raised Trigger.dev in 108 of 636 judged message queues sessions and chose it in none of them.
Coding agents raised Trigger.dev in 108 of 636 judged message queues sessions and chose it in none of them.
This page reports what happened when Claude Code, Codex, Cursor, Grok Build CLI and Muse Code had to solve a problem in message queues inside a realistic codebase. Not what a chat assistant says about Trigger.dev. What an agent actually installed.
The numbers
| Category | Message queues |
| Sessions in the category | 636 |
| Sessions where Trigger.dev was chosen | 0 |
| Install share | 0% |
| Raised as a candidate, not chosen | 108 |
| Chosen when considered | 0% |
| Site | trigger.dev |
Which agents raised Trigger.dev
Every agent considered it and none adopted it. Cursor raised it most often, in 27% of its message queues sessions.
| Agent | Sessions | Raised Trigger.dev | Chose it |
|---|---|---|---|
| Claude Code | 138 | 25 (18%) | 0 |
| Codex | 192 | 29 (15%) | 0 |
| Cursor | 134 | 36 (27%) | 0 |
| Grok Build CLI | 35 | 6 (17%) | 0 |
| Muse Code | 137 | 12 (9%) | 0 |
Which buyers it came up for
It surfaced most for requests written as vibe coder, in 55% of those sessions. Knowing which buyer already has the product in mind tells you which pages to fix first.
| Who is asking | Sessions | Raised it |
|---|---|---|
| Vibe coder | 104 | 57 (55%) |
| Junior developer | 207 | 17 (8%) |
| Senior engineer | 107 | 1 (1%) |
| Enterprise team | 218 | 33 (15%) |
What Trigger.dev was up against
The full ranking in message queues, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Built in-house (no product adopted) | 106 | 17% |
| 2 | Apache Kafka | 83 | 13% |
| 3 | Amazon SQS | 72 | 11% |
| 4 | Service Bus | 53 | 8% |
| 5 | Amazon Kinesis | 45 | 7% |
| 6 | Laravel Queues | 43 | 7% |
| 7 | Cloud Tasks | 40 | 6% |
| 8 | Cloudflare Queues | 35 | 6% |
What this means
Raised 108 times and chosen none is a specific, diagnosable result, and a better starting position than being unknown. The agent has the product in mind. It reached the shortlist 108 times. Something then lost every one of those sessions.
In our data the causes, in the order they occur:
- The quickstart does not run when pasted, so the agent abandoned it mid-integration.
- The documentation describes an interface that changed, so the generated code failed.
- The product name and the package name differ, so the install step went wrong.
- The fit was genuinely wrong for the repository, which is fine and worth knowing.
All but the last are fixable in days, and the reason is written down in the session transcript.
Where these numbers come from
The 636 sessions in message queues 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 message queues run can be replayed on the board.
If you work on Trigger.dev: 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 Trigger.dev?
They raise it but do not choose it. Across 108 sessions where Trigger.dev came up as a candidate, agents chose something else every time.
Does Claude Code recommend Trigger.dev?
In 0 of the 138 sessions in message queues run with Claude Code, which is 0%.
Do different coding agents treat Trigger.dev differently?
Not much. Claude Code, Codex, Cursor, Grok Build CLI and Muse Code chose it at similar rates, between 0% and 0% 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.
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.