We had to upgrade our 56TB Aurora Postgres cluster by 31 July without taking Trigger.dev down. Instead of moving the database, we made the problem smaller: new runs and the control plane went to PlanetScale, and the old runs stayed behind.

Copy a project-aware prompt that connects your coding agent to Trigger.dev's MCP server, with a CLI fallback and live setup progress.

Trigger.dev is the open source platform for building AI workflows in TypeScript. Long-running tasks with retries, queues, observability, and elastic scaling.

Show, hide, and reorder the columns on the runs list, and add smart columns that pull a value out of a run's payload, metadata, or output by JSON path. Your layout lives in the URL, so a view is bookmarkable and shareable.

Create as many keys as you need per environment, each with its own access scope, optional task restrictions, and an expiration date. Revoke any one instantly without rotating the rest.

Trigger.dev is the open source platform for building AI workflows in TypeScript. Long-running tasks with retries, queues, observability, and elastic scaling.

A server-computed verdict on whether work is starting, whether the runs that start are succeeding, and whether your telemetry is fresh, each with a suggested next action. Run it from the CLI, the get_report MCP tool, or the API.

Your prompts live in code, versioned on every deploy. Change the text or model from the dashboard without redeploying, and trace every generation back to the exact version that produced it.

Your coding assistant can now chat with your deployed agents, manage prompt versions, query your run data with TRQL, and pull a health report for any environment.

Every LLM call your tasks make is recorded with its model, cost, tokens, and latency. See the whole workload on a dashboard, open any single call in the run trace, and query all of it yourself.

Every conversation gets its own stateful machine that sticks around for the entire chat, sleeping and waking when needed.

If your team signs in with SSO, member provisioning is now automatic. Assign someone to Trigger.dev in your identity provider and they're added to your org; unassign them and their access is revoked.

Every conversation gets its own stateful machine that sticks around for the entire chat, sleeping and waking when needed.