Report card

Do AI agents pick Trigger.dev?

How often agents choose Trigger.dev when a developer needs background jobs & queues — measured across Claude, GPT, Gemini.

Trigger.dev

#4 of 5 queues
0%Pick Rate
95% CI 0%1%

When developers ask an AI agent for queues, Trigger.dev is picked 0% of the time — ranking #4 of 5 measured across Claude, GPT, Gemini.

Picked 0% Named, not picked 5% Never surfaced 95%

Beaten by BullMQ (27%), Temporal (6%), Inngest (2%).

Awareness

611K package downloads / week

Thin presence in the data models learn from — an awareness problem. Get into more code, docs, and developer discussion.

0 docs in FineWeb (10BT sample) · 181 URLs in Common Crawl

In the raw web crawl, but thin in the filtered corpus models actually train on — an awareness gap at the source.

Agent readiness

Level 1 · Basic Web Presence · 3/16 agent standards

Trigger.dev is missing Link headers, DNS-AID records, Markdown for agents, Content Signals. Readiness is what a site publishes for agents, not whether agents pick it — across our corpus the two barely correlate. Scored by Cloudflare's Agent Readiness score.

AdoptionDid the pick convert to installs? Public Adoption = npm downloads of your packages. The proof half of the funnel.

2.2M installs / month ▲ 3% MoM

Installs are roughly flat month over month.

Get the full report

The per-model and per-surface breakdown for Trigger.dev — where it wins, where it loses, and to whom — plus an alert when the Pick Rate moves.

About Trigger.dev

A background jobs and task queue platform for running long-running code outside of normal request cycles.

Trigger.dev lets developers define and run background jobs, scheduled tasks, and event-driven workflows directly in their codebase. It handles queuing, retries, logging, and observability so teams can offload work that would otherwise time out in serverless functions or block web requests. It targets Node.js developers building applications that need reliable async task execution.

Where to start

Install the Node.js SDK and connect it to a Trigger.dev project to start defining jobs in your codebase. The Trigger.dev dashboard provides visibility into job runs, logs, and failures.

Install

Links and summary verified from public sources.

The rest of the Background Jobs & Queues ranking

← Full Background Jobs & Queues leaderboard · How this is measured

Trigger.dev — do AI agents pick it? · Pickrate