# Do coding agents recommend Temporal? > Temporal was chosen in 4% of 681 judged agent frameworks sessions, ranking fourth. Measured with Claude Code, Codex and Cursor. Source: https://armature.tech/library/do-coding-agents-recommend-temporal Published: 2026-09-03 Publisher: Armature, Inc. (https://armature.tech) --- > Temporal was chosen in 4% of 681 judged agent frameworks sessions, ranking fourth. It was also raised as a candidate in 135 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 Temporal. What an agent actually installed. ## The numbers | | | | --- | --- | | Category | Agent frameworks | | Sessions in the category | 681 | | Sessions where Temporal was chosen | 29 | | Install share | 4% | | Rank in category | 4 of 35 | | Codebases it won in | 6 | | Raised as a candidate, not chosen | 135 | | Chosen when considered | 18% | | Site | temporal.io | ## By agent The three agents land within 7 points of each other on Temporal, which is closer than most products in this experiment manage. | Agent | Sessions | Chose Temporal | Share | | --- | --- | --- | --- | | Claude Code | 237 | 8 | 3% | | Codex | 243 | 19 | 8% | | Cursor | 201 | 2 | 1% | ## By who was asking Temporal performs similarly across the four kinds of buyer, from 0% to 10%. That is unusual: the category leader changed with the persona in 14 of the 18 categories we measured. | Who is asking | Sessions | Chose Temporal | Share | | --- | --- | --- | --- | | Vibe coder | 163 | 0 | 0% | | Junior developer | 157 | 0 | 0% | | Senior engineer | 254 | 26 | 10% | | Enterprise team | 107 | 3 | 3% | ## What Temporal 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 **(this page)** | 29 | 4% | | 6 | Prism | 28 | 4% | | 7 | OpenAI Agents SDK | 24 | 4% | | 8 | LangGraph | 23 | 3% | ## What this means This is an integration problem, not a presence problem. Agents raised Temporal in 135 sessions and chose it in 29, so it reaches the shortlist and then loses. Something at the last step is costing the session, and in our data that is usually a quickstart that does not run when pasted, documentation describing an interface that changed, or a package name that does not match the product name. That is the cheaper of the two problems to have. The reason is written down in each losing transcript. ## Where these numbers come from The 681 sessions in agent frameworks are part of a published set of 5,292, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: [how we measured this](/library/how-we-measured-this). Every agent frameworks run can be replayed on [the board](/leaderboards/agent-frameworks). If you work on Temporal: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts. ## Common questions ### Do coding agents recommend Temporal? Yes. Temporal was chosen in 29 of the 681 judged sessions in agent frameworks, a 4% install share, ranking fourth in its category. ### Does Claude Code recommend Temporal? In 8 of the 237 sessions in agent frameworks run with Claude Code, which is 3%. ### Do different coding agents treat Temporal differently? Not much. The three agents chose it at similar rates, between 1% and 8% of their runs. ### How was this measured? Real coding agents at pinned versions were run in sandboxes inside 51 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 Temporal considered but not chosen? It was raised as a candidate in 135 sessions without being chosen, and chosen in 29. That is a 18% conversion from considered to chosen. ## Read next - [How to get picked for agent frameworks by coding agents](https://armature.tech/library/agent-frameworks-coding-agents-playbook) (Markdown: https://armature.tech/library/agent-frameworks-coding-agents-playbook.md) - [Do coding agents recommend Vercel AI SDK?](https://armature.tech/library/do-coding-agents-recommend-vercel-ai-sdk) (Markdown: https://armature.tech/library/do-coding-agents-recommend-vercel-ai-sdk.md) - [Do coding agents recommend Cursor SDK?](https://armature.tech/library/do-coding-agents-recommend-cursor-sdk) (Markdown: https://armature.tech/library/do-coding-agents-recommend-cursor-sdk.md) - [Do Claude Code, Codex and Cursor pick the same tools?](https://armature.tech/library/do-claude-code-and-codex-agree) (Markdown: https://armature.tech/library/do-claude-code-and-codex-agree.md) --- Armature helps software products get discovered and used by coding agents. Service: https://armature.tech/discoverability · Results: https://armature.tech/leaderboards/sectors · Contact: contact@armature.tech