triggerdotdev / trigger.dev
trigger.dev
Trigger.dev – build and deploy fully‑managed AI agents and workflows
triggerdotdev / trigger.dev
Trigger.dev – build and deploy fully‑managed AI agents and workflows
Admin users viewing runs at /runs/<run_id> now automatically impersonate that run, letting them see exactly what end users see without manual setup.
Developers can now automatically track LLM costs across 145+ models directly in their traces, with a new inspector showing tokens, pricing, messages, and tool calls right in the span details.
The MCP server now offers 25 tools — up from 14 — enabling AI assistants to query data directly, switch between CLI profiles per-project, and control the dev server. A nasty build directory leak that was hoarding 842MB on disk has also been fixed.
Deployment operators can now promote older versions by passing allowRollbacks=true to the promote API, giving flexibility to rollback to known-good states without manual intervention.
High-concurrency batchTriggerAndWait processing no longer triggers LockAcquisitionTimeoutError, eliminating 880 daily errors and preventing parent runs from getting stuck.
The repository's vouched list has been updated to include a new member, likely granting them trusted contributor privileges or automated CI access.
Queues with concurrency keys now use a single wildcard entry in the master queue, preventing high-volume tenants from locking out others on the same shard.
The RunEngine documentation has been refreshed with a massive ASCII state diagram, updated terminology for regions, and the new token-based wait API.
Outside contributors are now required to open pull requests as drafts. Any standard pull request from a non-member is automatically closed until automated reviews and continuous integration checks pass.
The repository's internal configuration has been updated to include a new developer in its trusted contributors list.