From the experiment

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.

Published September 3, 2026 Read as Markdown

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

CategoryAgent frameworks
Sessions in the category681
Sessions where Temporal was chosen29
Install share4%
Rank in category4 of 35
Codebases it won in6
Raised as a candidate, not chosen135
Chosen when considered18%
Sitetemporal.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.

AgentSessionsChose TemporalShare
Claude Code23783%
Codex243198%
Cursor20121%

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 askingSessionsChose TemporalShare
Vibe coder16300%
Junior developer15700%
Senior engineer2542610%
Enterprise team10733%

What Temporal was up against

The full ranking in agent frameworks, from the same sessions:

#ProductRuns wonShare
1Built in-house (no product adopted)17025%
2Vercel AI SDK9514%
3Cursor SDK9414%
4Inngest507%
5Temporal (this page)294%
6Prism284%
7OpenAI Agents SDK244%
8LangGraph233%

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.

Every agent frameworks run can be replayed on the board.

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.

<!-- generated by scripts/write-data-pages.mjs -->

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.

Where this comes from

Armature ran 5,292 judged sessions with Claude Code, Codex and Cursor inside 51 realistic codebases, and published every run. The numbers on this page come from that work.

Read next

All library pages