Do AI agents pick Temporal?
How often agents choose Temporal when a developer needs background jobs & queues — measured across Claude, GPT, Gemini.
95% CI 2%–10%
When developers ask an AI agent for queues, Temporal is picked 5% of the time — ranking #2 of 5 measured across Claude, GPT, Gemini.
4.5M package downloads / week
0 docs in FineWeb · 468 URLs in Common Crawl
16.1M installs / month ▲ 11% MoM
Get the full report
The per-model and per-surface breakdown for Temporal — where it wins, where it loses, and to whom — plus an alert when the Pick Rate moves.
About Temporal
A durable execution platform for running reliable, long-running workflows in code.
Temporal lets developers write workflows as ordinary code that automatically survives failures, retries, and service restarts without manual state management. It handles the orchestration of distributed work — tasks, queues, timers, and retries — so application logic stays simple even when the underlying infrastructure is unreliable. It is aimed at backend engineers building anything from microservice orchestration to long-running business processes.
Where to start
Developers typically run a Temporal server (locally via Docker or via Temporal Cloud) and then use a language SDK to write and register workflow and activity code. The TypeScript SDK client sub-package is used to connect to the server and start or signal workflows programmatically.
The rest of the Background Jobs & Queues ranking
| 1 | BullMQ | 17% |
| 3 | Inngest | 2% |
| 4 | Trigger.dev | 0% |
| 5 | Graphile Worker | 0% |