@trigger.dev/sdk
4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed
180 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
4.8.8
20 Nov 2026The MCP
list_runstool can now filter runs by queue, batch, schedule and bulk action, and its descriptions now say thatperiodtakes precedence overfromandto.When OIDC token requests are still throttled after retries,
auth.getOIDCToken()now throwsRateLimitErrorwith codeRATE_LIMIT_EXCEEDEDfor both per-run and shared API limits. If you catch these errors withinstanceof OIDCTokenError, check forRateLimitErrorinstead. Other OIDC errors and retry behavior are unchanged.Stop losing a run's suspend when the supervisor's first attempt to hand it off fails unexpectedly.
trigger.dev v4.8.8
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.8.8Release notes
Read the full release notes: trigger.dev/changelog/v4-8-8
Improvements
The MCP
list_runstool can now filter runs by queue, batch, schedule and bulk action, and its descriptions now say thatperiodtakes precedence overfromandto.When OIDC token requests are still throttled after retries,
auth.getOIDCToken()now throwsRateLimitErrorwith codeRATE_LIMIT_EXCEEDEDfor both per-run and shared API limits. If you catch these errors withinstanceof OIDCTokenError, check forRateLimitErrorinstead. Other OIDC errors and retry behavior are unchanged.Stop losing a run's suspend when the supervisor's first attempt to hand it off fails unexpectedly.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
The remote MCP server can now list the tags used on your runs, search and read your logs, add tags, update metadata, reset idempotency keys and reschedule delayed runs, and run details now include the run's metadata values. It can also list, read, create and abort bulk actions that cancel or replay many runs at once, and you approve every bulk action it creates. It can also read what a run streamed. Edits that would change nothing are refused without asking you to approve them.
The dashboard now shows only the last four characters of root API keys for all projects. Existing root keys still work, but you can no longer copy them from the dashboard. Create a separate API key for each new integration.
The remote MCP server now offers new OAuth scopes for errors, queues, tasks, batches, waitpoints, environments, deployments, branches, environment variable names and project settings. Existing connections keep the access they already have.
External OIDC token requests now count against the same environment rate limit as other API requests, with the per-run limit unchanged.
A run's Session link now opens the session at that run.
Reopening the time filter keeps an exact date range selected instead of switching back to "in the last".
All packages: v4.8.8
@trigger.dev/build, @trigger.dev/convex, @trigger.dev/core, @trigger.dev/linear, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, @trigger.dev/slack, trigger.dev
4.8.7
19 Nov 2026Sessions and
chat.agentnow accept the object form ofconcurrencyKeyintriggerConfig, giving each concurrency limit its own key, the same astask.trigger().Fix runs failing with
TASK_DID_CONCURRENT_WAITon their first wait whenprocessKeepAliveis enabled.Fix
chat.agentchannels on AI SDK 7 failing the whole turn when a channel file can't be downloaded. A file the connector owns but can't read is now replaced with an[Attached file "…" could not be loaded]note and the agent still answers, as it does on AI SDK 6. AI SDK 7 describes a file's URL in a tagged form that the SDK didn't recognise, so the failed file was never found.An inline
data:file in a channel message is no longer passed to a connector'sdownload, and on AI SDK 6 it reaches the model instead of failing the turn.
trigger.dev v4.8.7
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.8.7Release notes
Read the full release notes: trigger.dev/changelog/v4-8-7
Improvements
Sessions and
chat.agentnow accept the object form ofconcurrencyKeyintriggerConfig, giving each concurrency limit its own key, the same astask.trigger().
Bug fixes
Fix runs failing with
TASK_DID_CONCURRENT_WAITon their first wait whenprocessKeepAliveis enabled.Fix
chat.agentchannels on AI SDK 7 failing the whole turn when a channel file can't be downloaded. A file the connector owns but can't read is now replaced with an[Attached file "…" could not be loaded]note and the agent still answers, as it does on AI SDK 6. AI SDK 7 describes a file's URL in a tagged form that the SDK didn't recognise, so the failed file was never found.An inline
data:file in a channel message is no longer passed to a connector'sdownload, and on AI SDK 6 it reaches the model instead of failing the turn.Fix two compaction problems on AI SDK 7. After a compaction, a
chat.agentturn that continued a tool approval sent the model the full pre-compaction transcript instead of the summary, which undid the compaction (this also affectedchat.MessageAccumulator). And between-turn compaction, inchat.agentandchat.createSession, was asked about the whole turn's token usage instead of the last step's, soshouldCompactthresholds triggered too early on multi-step turns.If you call
compactIfNeededon achat.MessageAccumulator, pass it the last step's usage,(await result.steps).at(-1)?.usage.result.usageis the turn's sum on AI SDK 7.Fix
chat.agentsteering on AI SDK 7. A steering message thatpendingMessages.prepareturns into asystemmessage no longer makes the step fail with an invalid-prompt error:chat.toStreamTextOptions()now setsallowSystemInMessages: true, as AI SDK 5 and 6 already behave (passallowSystemInMessages: falseafter the spread to keep AI SDK 7's strict default). A turn whose stream ends on an error now reportsfinishReason: "error"inonTurnComplete, where it could beundefinedor the previous step's reason.Fix a
chat.agenttool result containing aBigIntfailing the next turn's model call in apps that defineBigInt.prototype.toJSON. It is now sent as the JSON thattoJSONgives, in the next step and in later turns.Fix
chat.agentfailing the next step or turn withAI_InvalidPromptError("The messages do not match the ModelMessage schema") when a tool returned a value that isn't plain JSON, such as aDatefrom an ORM row. On AI SDK 6, and AI SDK 7 before 7.0.101, tool results are now converted to JSON the way newer AI SDK versions do it, so aDatereaches the model as its ISO string. A value JSON can't hold, such as aBigIntor a circular reference, is replaced by an error result that names the tool and the field, and the same error is logged on the run.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Worker registration now refuses task source files that are too large once decompressed or aren't valid text, with an error that names the file.
The session page now says when earlier conversation messages couldn't be loaded, with a retry, and closing a session keeps the view you were on.
On a live run's trace, "Errors only" and search now pick up a span that fails or gets a new name after it first appeared.
Alert webhook URLs that point at private or reserved network addresses are now rejected in more cases.
All packages: v4.8.7
@trigger.dev/build, @trigger.dev/convex, @trigger.dev/core, @trigger.dev/linear, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, @trigger.dev/slack, trigger.dev
4.8.6
18 Nov 2026Allow an explicit audience when signing and verifying JWTs and user-actor tokens.
Deploys on the
bun-1.4runtime now compile the run worker and your task files into a Bun executable with bytecode, so runs start faster.import.meta.urland__dirnamestill point at your files under/app, so files you read next to your code must be in the image as before (e.g. withadditionalFiles). Setbuild.bunBytecode: falseintrigger.config.tsto turn compilation off.trigger devandtrigger deployno longer crash withspawn ... ENOENTon bun runtimes when Bun isn't installed at~/.bun. The CLI now falls back tobunon yourPATH(Homebrew, mise and similar installs), and if Bun still can't be started,trigger devreports a readable error andtrigger deployskips local skill discovery with a warning and carries on.
trigger.dev v4.8.6
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.8.6Release notes
Read the full release notes: trigger.dev/changelog/v4-8-6
Highlights
Allow an explicit audience when signing and verifying JWTs and user-actor tokens.
Improvements
Deploys on the
bun-1.4runtime now compile the run worker and your task files into a Bun executable with bytecode, so runs start faster.import.meta.urland__dirnamestill point at your files under/app, so files you read next to your code must be in the image as before (e.g. withadditionalFiles). Setbuild.bunBytecode: falseintrigger.config.tsto turn compilation off.trigger devandtrigger deployno longer crash withspawn ... ENOENTon bun runtimes when Bun isn't installed at~/.bun. The CLI now falls back tobunon yourPATH(Homebrew, mise and similar installs), and if Bun still can't be started,trigger devreports a readable error andtrigger deployskips local skill discovery with a warning and carries on.Bundled task files now keep their project layout (for example
/app/src/trigger/tasks.mjs) when the CLI runs from outside the project, such asnpx trigger.dev deploy. Before, they could land under a path containing the project's location, away from the filesadditionalFilescopies next to them, so reads relative toimport.meta.urlfailed.Show CLI command errors in the same error format as other CLI errors, and keep them visible with
--log-level error.Deploys now report a warmup command that loads your config and task files offline without running any task, so the platform can prepare faster run starts for your deployment.
Generate the machine ID and the managed run controller ID on first use instead of at import, so importing these modules draws no randomness and a process restored from a warm start does not reuse IDs drawn before it was saved.
Deploys on the
node-24andnode-26runtimes now build a Node compile cache for your bundled code during the image build, so runs spend less time compiling your tasks and their dependencies before they start.node-22deploys are unchanged.Report a run whose process the kernel killed for running out of memory as
TASK_PROCESS_OOM_KILLED, rather than as a generic exit afterSIGKILL, when the out-of-memory kill is counted in the run's cgroup.Deployed task processes now receive secret environment variables only with the run, instead of also in the environment the process starts with.
Deployed task processes now start with the environment variables that Node, OpenSSL, libuv or the dynamic loader read only at startup (such as
LD_PRELOAD,OPENSSL_CONF,NODE_ICU_DATA,TZandUV_*), and the run's logs warn, by name only, about other startup-only variables (such asNODE_OPTIONS,MALLOC_*orGLIBC_TUNABLES) that arrive too late to take effect.Builds from
trigger devandtrigger deploynow use esbuild 0.28. TypeScript parameter properties are now emitted as class fields, and source map paths are URL-encoded.webhooks.notion()endpoints accept Notion's verification request. While the endpoint has no signing secret, theverification_tokenNotion sends is stored as its signing secret, so you can paste it back into Notion and later deliveries verify with it. Redeploy with this version for existing Notion endpoints to pick it up.Support scoped run tokens without an environment key, including offloaded task inputs and stream waits. Explain why a run has no usable credential for an operation.
Public-token helpers and chat token creation now prefer server minting for root API keys too, avoiding the legacy claims endpoint on compatible servers. Trigger, batch, and waitpoint responses missing a token also try server minting first.
Root-key callers retain local-signing compatibility only when the mint endpoint is missing or an older server specifically rejects an empty scope list. Named API keys and run tokens never self-sign. Authorization failures, expiration validation errors, rate limits, and server or connection failures do not activate the fallback.
Server minting with a root key signs with that same authenticated key, including during its rotation grace period, rather than with its replacement. Tokens stop authenticating when that key's grace period ends or it is immediately revoked. Deploy this server update before upgrading the SDK if you rely on minting during root-key rotation; older servers can still reject grace-window keys.
Server-minted tokens use the API rate-limit budget and follow the server's expiration rules, including its 30-day maximum. Minting tokens without scopes requires self-hosted v4.8.4 or later unless the root-key compatibility fallback is available. The default expiration remains 15 minutes.
chat.agentnow passeschatId,turnandclientDatato the callbacks an agent can call a model from, so a mock model injected throughclientDatareaches them. The compactionsummarizethat runs throughchat.MessageAccumulator.prepareStep()and achat.createSessionturn'sprepareStep(),onCompacted,onValidateMessages, and thependingMessagesonReceivedandonInjectedcallbacks previously lacked it. ThemockChatAgentturn methods (sendMessage,sendRegenerate,sendAction) now also wait foronTurnCompleteand the transcript save to finish, so tests can assert on what those hooks recorded without a sleep.concurrencyKeynow also takes an object, so one run can be limited by two limits keyed by different things, like a cap per session and a cap per organization.defaultis the run's own key and every other entry gives a named limit its own key:concurrencyKey: { default: sessionId, [orgLimit.name]: orgId }. A string key works as before.
Bug fixes
Fix
child_process.fork()andspawn(process.execPath, ...)in compiledbun-1.4deploys. They started the run worker again instead of Bun, so the child never ran and the task hung.process.execPathnow points at the image'sbunbinary, as it does in uncompiled deploys.Fix webhook verification for
webhooks.brex(), which now reads thewebhook-id,webhook-timestampandwebhook-signatureheaders Brex sends instead ofsvix-*headers, and forwebhooks.composio(), which now keys the signature with the secret's raw text as Composio does instead of base64-decoding it. PagerDuty, Sentry, Vercel, Zendesk, Attio, DocuSign and Intercom endpoints now default to pasting the provider-issued signing secret, and Linear and Calendly offer both generating and pasting one. Redeploy with this version for existing endpoints to pick up the change.Fix
chat.agenton AI SDK 7 sending the model the same input on every step. Once a step'sprepareStepreturned messages (a steering message, a mid-turnchat.inject, context compaction, or your ownprepareStep), later steps no longer included the newest tool results, so the model kept repeating the same tool call until the step limit.If you call
chat.compact()from your ownprepareStep, pass it theresponseMessagesyourprepareStepreceives (chat.compact(messages, steps, { ...options, responseMessages })) so steps after a compaction are rebuilt correctly on AI SDK 7.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Ask the Dashboard Agent to watch something, such as a deploy, a task or a model, and it proposes alerts you confirm one by one. When the alerts belong together, it offers to create them as one grouped alert in a single click.
Dashboard widget menus now have a Watch action that starts an alert from the widget's query, and when the query cannot be alerted on as written or the dashboard has filters applied, the Dashboard agent helps adapt it. The Watch button in the dashboard header is removed.
Select up to 100 environment variable values on the Environment variables page and delete them together. The confirmation lists every value and its environment, and asks you to type a word before anything is removed.
Compare the environment variables of two environments on the Environment variables page and see only the keys that differ, with secrets shown as the same or different but never revealed. Copy values from one environment to the other, one key or up to 100 at a time.
Click a key on the environment variables page to see its value in every environment and preview branch in a side panel, with edit and delete in place. A list showing a single environment can also be sorted by last updated. The edit dialog now starts in the value field, and archived preview branches are no longer accepted as targets.
Environment variables page: a new Needs attention page lists the keys in one environment that are empty, missing compared with your other environments, changed in the last day, or replaceable with OIDC, with copy, delete and ignore actions. The OIDC page is now a grid of providers with setup in a side panel, it points at environment variables OIDC could replace, and there are setup guides for Azure, Google Cloud, HashiCorp Vault, Doppler, Snowflake and Databricks.
Add opt-in per-environment encryption keys for runtime and build environment variables, with rotation and migration support.
Add "Ignored branches" to the Git settings: pull requests from branches matching these patterns no longer get a preview deployment. Patterns are globs matched against the whole branch name, like
dependabot/**.The OIDC page lists Hugging Face and OpenRouter, and the environment variables page suggests OIDC for their API keys. Each has a setup guide in the docs.
Organization owners can now require multi-factor authentication for every member, and ask for a fresh MFA check before members view environment variables, create personal access tokens or change the organization's security settings. Find both under Organization settings → Security.
Add a hosted MCP server so AI clients can work with your projects and runs. It is opt-in per deployment.
The allowed IP addresses field on API keys now turns each address or CIDR range into its own pill as you type, checks it right away with the same rules used on save, and lets you remove entries one at a time. A "Test an IP" button checks whether an address would be allowed by the current list before you save.
The assistant can now list alerts across environments and projects, and show which alert channels are set up.
Environment variables page: after adding a variable, the list switches to the environment you saved it in and opens the page that holds the new key, with a toast naming where it went. The
envfilter in the URL also acceptsdevelopment,stagingandproduction. The compare view has a copy button on each key, and each row's edit and delete buttons are named after the key and environment for screen readers.Runs started through the hosted MCP server are now recorded with the
mcp-remotetrigger source, so they can be told apart from runs started by the local CLI MCP.Personal access tokens created on the dashboard can now expire on a custom date, picked from a calendar alongside the preset lifetimes. A token expires at the end of the chosen day (UTC), up to the longest offered lifetime.
A scheduled task's schedules now have their own tab next to Runs, with every column visible. The side panel shows the schedule when the task has exactly one, and a count with a link when it has more. Next run shows the local time first, followed by the relative time.
Runs start faster when the platform is busy.
The alert group page now shows its header and member list right away, and member charts fill in as they load.
The alert wizard now highlights the suggested option on choice steps instead of the first row.
The alerts list now shows its rows before the activity sparklines load, and the sparklines load faster.
Alerts created from the Dashboard Agent are now limited to 200 active alerts per project, with bounded names, scopes and notification channels.
The dashboard agent now asks you to confirm before resolving an alert.
The Dashboard Agent can now look up runs, deployments and queries in non-development environments for members whose role can see them but can't view API keys.
Help links (
?aiHelp=,/ai-help) now prefill the chat composer instead of sending.Fix dashboard pages that open as a dialog (such as adding environment variables or a new alert) re-rendering the whole page when loaded directly or reloaded.
Saving an environment variable that someone else deletes at the same moment now shows a clear message asking you to try again instead of a database error, and the API answers with a 409. Deleting a value can no longer remove a value that was being added to the same variable at that moment.
Runs that exhaust their dequeue attempts while the run or its environment can't be read now fail with
TASK_RUN_DEQUEUED_MAX_RETRIESinstead of staying queued forever.Fix waitpoint callback URLs returning authentication errors when created inside preview branch runs, including previously issued URLs.
Restore offloaded payload, output, and stream-wait result downloads for API keys with packet read access.
Keep waitpoint idempotency keys scoped to a run unless the API key can both read and write all waitpoints.
An organization's only Owner can no longer leave or be removed while other members remain, so the organization always keeps someone who can manage members, billing and roles.
Numbered pagination no longer repeats a page number on long lists, and the Tasks page now keeps its page numbers in one bar fixed below the table.
Revoking or expiring a personal access token now also ends the environment JWTs exchanged from it and the run, batch and session tokens minted with them.
Runs triggered in the seconds after a deploy no longer get stuck waiting for a version until the next deploy.
A run released from waiting for a version is no longer occasionally left queued with nothing to pick it up when a worker dequeues it at the same moment.
Fix sandbox task retries stalling when retry delays are short.
A task that returns while its run is resuming from a wait it did not await (for example a wait raced against a timeout or an abort signal) can now fail right away with an error that says so. Before, the run stayed in an executing state until its heartbeat timed out, and could then be reported as out of memory. This is off by default: set
RUN_ENGINE_STALE_COMPLETION_MODE=enforceon the webapp to switch it on.
All packages: v4.8.6
@trigger.dev/build, @trigger.dev/convex, @trigger.dev/core, @trigger.dev/linear, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, @trigger.dev/slack, trigger.dev
4.8.5
12 Nov 2026- Security
Deployed tasks on the
node,node-22,node-24andnode-26runtimes now run on Node.js 22.23.5, 24.22.3 and 26.13.1, the November 2026 security releases. They fix several high severity issues in HTTP/2 and TLS, including CVE-2026-123863, CVE-2026-123864, CVE-2026-123865, CVE-2026-123866, CVE-2026-123872 and CVE-2026-123874, plus CVE-2026-126051 on Node.js 24 and 26. Existing deployments keep the old runtime until you redeploy with this version. The webapp and supervisor images now run on Node.js 24.22.3, the November 2026 security release.
This is a security release. Update the CLI and redeploy to pick up the fixes.
Most tasks are not affected. The high severity issues only matter if your task code, or a package it uses, runs an HTTP/2 or HTTPS server inside the task. Regular outbound calls with
fetch,node:httpornode:https(calling APIs, databases or LLM providers) are not affected by them.Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.8.5Release notes
Read the full release notes: trigger.dev/changelog/v4-8-5
Improvements
- Security
Deployed tasks on the
node,node-22,node-24andnode-26runtimes now run on Node.js 22.23.5, 24.22.3 and 26.13.1, the November 2026 security releases. They fix several high severity issues in HTTP/2 and TLS, including CVE-2026-123863, CVE-2026-123864, CVE-2026-123865, CVE-2026-123866, CVE-2026-123872 and CVE-2026-123874, plus CVE-2026-126051 on Node.js 24 and 26. Existing deployments keep the old runtime until you redeploy with this version.
Server changes
These changes affect the self-hosted Docker image:
The webapp and supervisor images now run on Node.js 24.22.3, the November 2026 security release.
All packages: v4.8.5
@trigger.dev/build, @trigger.dev/convex, @trigger.dev/core, @trigger.dev/linear, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, @trigger.dev/slack, trigger.dev
4.8.4
10 Nov 2026Add opt-in AWS session tags with
awsCredentialProvider({ sessionTags: true })for task-level IAM restrictions and attribute-based permissions. Tags come from the verified run identity. Update the role trust policy to allowsts:TagSessionbefore enabling them; existing integrations remain untagged.Logins made with
trigger.dev loginor the MCP server now stop working after 7 days without use. When that happens, the CLI and the MCP server start a new login instead of failing with an auth error, and in CI the CLI says to log in again. Self-hosted instances can change the window withCLI_LOGIN_IDLE_TIMEOUT_DAYS, or set it to0to turn it off for new logins. Logins made before this change aren't affected.Add
infisicalAccessTokenat@trigger.dev/sdk/oidc/infisicalto authenticate tasks with Infisical using OIDC instead of stored credentials. Supports US, EU, and self-hosted instances, custom audiences, and Infisical organization scoping.
trigger.dev v4.8.4
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.8.4Release notes
Read the full release notes: trigger.dev/changelog/v4-8-4
Highlights
Add opt-in AWS session tags with
awsCredentialProvider({ sessionTags: true })for task-level IAM restrictions and attribute-based permissions. Tags come from the verified run identity. Update the role trust policy to allowsts:TagSessionbefore enabling them; existing integrations remain untagged.
Improvements
Logins made with
trigger.dev loginor the MCP server now stop working after 7 days without use. When that happens, the CLI and the MCP server start a new login instead of failing with an auth error, and in CI the CLI says to log in again. Self-hosted instances can change the window withCLI_LOGIN_IDLE_TIMEOUT_DAYS, or set it to0to turn it off for new logins. Logins made before this change aren't affected.Add
infisicalAccessTokenat@trigger.dev/sdk/oidc/infisicalto authenticate tasks with Infisical using OIDC instead of stored credentials. Supports US, EU, and self-hosted instances, custom audiences, and Infisical organization scoping.Deploy from GitHub Actions using Trusted publishing and GitHub OIDC without storing a Trigger.dev API key. These deployments run entirely on the build server and do not grant the CLI access to environment variables.
Use GitHub Actions trusted publishing with
preview archiveandpromote, without storing API keys. Preview deploys for closed or merged pull requests now archive their branch.preview archivealso supports Preview environment API keys throughTRIGGER_ACCESS_TOKEN.Failed Preview archive operations now exit with an error for API-key and personal-token authentication too, including automatic cleanup during deploys. CI cleanup jobs that previously passed despite an archive failure will now fail. Concurrent cleanup jobs succeed when another job has already archived the same branch generation.
Add a bundled agent skill for integrating Trigger.dev with Convex, including transactional triggering, Realtime progress, recovery, and scoped-token safety. Install it manually from the package; it is not part of the CLI skills installer.
Self-hosted supervisors that run tasks in microVMs can now have a finished run's suspend snapshots deleted from shared storage, instead of leaving them behind. The server-only checkpoint client gains a
deleteSnapshotscall for this.Browser realtime subscriptions now resume reliably after the tab is hidden and shown again. This comes from upgrading
@electric-sql/clientto 1.3.0, which also lets apps that depend on 1.3.0 share a single copy with the SDK.Use run credentials for run results, rescheduling, schedules, and environment-variable operations inside tasks. Run credentials remain limited to the current environment: shared schedules cannot be changed, and parent environment variables cannot be written.
chat.agentnow accepts only two kinds of message from a chat client: user messages, and answers to tool calls the agent made. A tool approval or tool output is merged onto the stored call it answers and runs with the input from the agent's own history, so a client can't add tool calls or change a call's input.chat.headStartdrops tool calls from the history the client sends, andupsertIncomingMessageonly adds user messages.Create public tokens without scopes from inside tasks using run credentials, without requiring an environment secret key.
Bug fixes
Fix logs and spans with large numeric object keys failing to ingest and dropping the rest of their batch.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
API keys can have custom access: combine access presets or set a level for each area, such as Runs or Deployments, optionally limited to selected tasks. Edit access changes what an existing key can do without rotating it, and the API keys page marks keys whose access differs from their preset today.
New API keys can expire on a custom date. Pick Custom date in the Expires menu and choose a day from the calendar; the key stops working at the end of that day in your local time zone.
Restrict an API key to a list of IP addresses so requests using it from anywhere else are rejected. Set the list when creating a key or edit it later from the API keys page, which now also shows the IP address each key was last used from.
Organizations can save custom API key access as a preset and reuse it when creating keys in any project. Saved presets appear under Your presets in the access picker, and organization Owners and Admins can save and delete them.
Click an API key to see its access, when it last used each area, and its details in a side panel. From there you can narrow a key to what it used in the last 30 days, without changing its secret.
Alerts can be grouped: select alerts in the list and create a group that raises when any or all of them fire, with its own channels and expiry. Members keep evaluating but notify only through the group. Groups can also be created through the API, with their members in one call.
Health alerts can now watch a chosen subset of checks — flow, execution and liveness — instead of all three.
Email the owner of a dashboard-created personal access token 7 days before it expires, and again when it has, so a CI deploy using it doesn't break by surprise. Set
PERSONAL_ACCESS_TOKEN_EXPIRY_EMAILS_ENABLED=falseto turn them off.Personal access tokens created on the dashboard now expire after the lifetime you choose (30, 90 or 365 days by default). Requests made with an expired token get an error that says when it expired and where to create a new one. Existing tokens keep working as before.
Alerts now require at least one channel (email, Slack or webhook). The option to notify the Dashboard Agent chat has been removed.
Choose an API key's expiry from presets or a calendar in one picker, with date previews and expiration at the end of the chosen day in UTC.
The API keys page shows when each key expires and when it was revoked, and the "How to set env vars" dialog no longer displays your secret key. Custom access is now a table of levels for each area, and options a key can't use are shown disabled with the reason.
The Environment variables page now filters by environment, opening on the environment you're in, with a picker for preview branches. Deleting a variable asks for confirmation first.
The side menu has a new Security section, just above Manage, that groups API keys, Environment variables, Trusted publishing and OIDC.
Alerts: Admins and Developers can delete alerts; health metric charts use straight segments.
Alert charts and alert evaluation are no longer limited by the plan's query period.
Project JWT minting now rejects expiration times longer than 24 hours.
Dashboard sessions past their deadline now end on their next request, including background data requests and form submissions, not only on page navigation.
Restore duration wait details and the Skip waitpoint action in the dashboard.
Fix the Logs page redirecting to Tasks when Logs is visible in the sidebar.
Fix a new project's first deploys failing with "Failed to get deployment image ref" when two of them start at the same time.
Triggering a task with a payload over the offload threshold from inside a running task works again. Run-scoped tokens and restricted API keys upload offloaded payloads into their own namespace and may only trigger with payloads they uploaded, while pointers at other runs' stored payloads or outputs are still rejected.
Stop runs that wait a long time for capacity from being requeued and started a second time while their first start is still pending.
Long GitHub organization and repository names on the Trusted publishing page now stay on one line and truncate, with the full name shown on hover.
All packages: v4.8.4
@trigger.dev/build, @trigger.dev/convex, @trigger.dev/core, @trigger.dev/linear, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, @trigger.dev/slack, trigger.dev
4.8.3
30 Oct 2026- Deprecated
Deprecates the legacy Bun runtime.
runtime: "bun"(and its explicit spelling"bun-legacy"), which deploys Bun 1.3.3 with Node.js 20 alongside it, now prints a deprecation warning, and deploys that use it will be rejected from January 5, 2027. Switch toruntime: "bun-1.4"(Bun 1.4.4 on an image with no Node.js binary) and redeploy. CLI and MCP logins are now bound to the machine that started them. Approving a login in your browser sends you back to the CLI automatically, or, when the browser is on another machine, shows a code to paste into the terminal (or pass with
trigger.dev login --code). Older CLI versions will need to upgrade to log in.Add
trigger webhooks set-secretandtrigger webhooks generate-secret, which store a webhook endpoint's signing secret without printing it.set-secretreads the secret from a pipe, an environment variable or a.envfile, andgenerate-secretsaves the new secret to an env file. When the endpoint already has a secret, both ask how long the old one keeps working (or take--previous-secret-ttl 24hin scripts). The MCP server'sset_webhook_secretandgenerate_webhook_secretdescriptions now point AI agents at these commands, so the secret stays out of the agent's context.
trigger.dev v4.8.3
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.8.3Release notes
Read the full release notes: trigger.dev/changelog/v4-8-3
Improvements
CLI and MCP logins are now bound to the machine that started them. Approving a login in your browser sends you back to the CLI automatically, or, when the browser is on another machine, shows a code to paste into the terminal (or pass with
trigger.dev login --code). Older CLI versions will need to upgrade to log in.Add
trigger webhooks set-secretandtrigger webhooks generate-secret, which store a webhook endpoint's signing secret without printing it.set-secretreads the secret from a pipe, an environment variable or a.envfile, andgenerate-secretsaves the new secret to an env file. When the endpoint already has a secret, both ask how long the old one keeps working (or take--previous-secret-ttl 24hin scripts). The MCP server'sset_webhook_secretandgenerate_webhook_secretdescriptions now point AI agents at these commands, so the secret stays out of the agent's context.- Deprecated
Deprecates the legacy Bun runtime.
runtime: "bun"(and its explicit spelling"bun-legacy"), which deploys Bun 1.3.3 with Node.js 20 alongside it, now prints a deprecation warning, and deploys that use it will be rejected from January 5, 2027. Switch toruntime: "bun-1.4"(Bun 1.4.4 on an image with no Node.js binary) and redeploy. Add
trigger.refresh(ctx, id)to request an earlier status check for a Convex-tracked run, so applications using Trigger Realtime can publish results without waiting for the next scheduled poll. Requests are coalesced and rate-limited, use the existing completion callback, and retain polling as a recovery fallback.Add private-beta OIDC authentication for deployed Cloud tasks, with an AWS credential provider and environment-specific setup instructions. Install
@aws-sdk/client-ststo use@trigger.dev/sdk/oidc/aws, upgrade your deployment CLI, and redeploy. Contact us to enable access for your organization.
Bug fixes
Fix parent and root metadata updates being lost after one update could not be applied. Only that update is now skipped, and the rest are written. Metadata keys that name only the root, such as
$.or$.., are now ignored on a run's own metadata instead of throwing, and rejected for parent and root metadata, which fails the whole request.Fix reloading a chat mid-turn after its access token was refreshed. A token refresh during a streaming turn persisted a resume cursor from the middle of the turn, so a reload resumed past chunks the page needed and failed to rebuild the assistant message ("No tool invocation found for tool call ID"). The persisted cursor now stays at the start of the turn until it completes, so a reload replays the whole turn.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
The CLI and MCP login consent page now shows when and from which IP address the login was started, and you get an email whenever a new CLI or MCP login is authorized on your account.
Searching, filtering to errors, and expanding or collapsing spans in the run trace view are faster on large traces.
Guide switching from shared root keys to individually managed API keys, while keeping root key regeneration directly available.
CLI and MCP login codes now work once, and every login mints its own personal access token instead of reusing an existing CLI token.
Fix run traces occasionally going missing when a span recorded an exception with no message, type or stack trace.
All packages: v4.8.3
@trigger.dev/build, @trigger.dev/convex, @trigger.dev/core, @trigger.dev/linear, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, @trigger.dev/slack, trigger.dev
4.8.2
29 Oct 2026- Breaking
Query dashboard APIs reject run tokens and public access tokens without user delegation. Existing API key access, including restricted keys with the required query scopes, is unchanged. MCP dashboard access remains supported through delegated tokens for current organization members.
- Breaking
The legacy
clickhouseevent store is retired: task events now go toclickhouse_v2. If you self-host withEVENT_REPOSITORY_DEFAULT_STORE=clickhouse, switch it toclickhouse_v2and follow the self-hosting guide to copy older events, which no longer show until you do. - Security
Upgrade
socket.io-clientto 4.8.4 so projects using the SDK and CLI installws8.21 instead of 8.17.1, which has published advisories (GHSA-96hv-2xvq-fx4p, GHSA-58qx-3vcg-4xpx). The old pin blocked upgradingwswithout a package manager override.
trigger.dev v4.8.2
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.8.2Release notes
Read the full release notes: trigger.dev/changelog/v4-8-2
Breaking changes
- Breaking
Query dashboard APIs reject run tokens and public access tokens without user delegation. Existing API key access, including restricted keys with the required query scopes, is unchanged. MCP dashboard access remains supported through delegated tokens for current organization members.
- Breaking
The legacy
clickhouseevent store is retired: task events now go toclickhouse_v2. If you self-host withEVENT_REPOSITORY_DEFAULT_STORE=clickhouse, switch it toclickhouse_v2and follow the self-hosting guide to copy older events, which no longer show until you do.
Improvements
Deployed tasks now keep a valid short-lived run token for their whole run: the token is refreshed during long runs and before a run resumes from a checkpoint. A warm-started task no longer keeps the previous run's token when the next run has none, and run credentials are left out of runner debug logs.
- Security
Upgrade
socket.io-clientto 4.8.4 so projects using the SDK and CLI installws8.21 instead of 8.17.1, which has published advisories (GHSA-96hv-2xvq-fx4p, GHSA-58qx-3vcg-4xpx). The old pin blocked upgradingwswithout a package manager override. Adds the
bun-1.4runtime.runtime: "bun-1.4"deploys on Bun 1.4.4 in a Bun-only image with no Node.js binary, and the run controller itself runs under Bun.runtime: "bun"is unchanged (Bun 1.3 with Node.js alongside it);bun-legacyis accepted as an explicit spelling of the same runtime. On Bun 1.4 the worker no longer crashes at startup on the--no-warnings=ExperimentalWarningflag.Add an experimental Convex component for triggering tasks transactionally and reading their status and results through reactive queries, without configuring webhooks.
Run metadata operations now reject JSON-path keys that use escaped dots to reach
__proto__,constructororprototype.Use short-lived run tokens for supported SDK operations inside deployed tasks when available, retaining environment-key compatibility for unsupported operations and missing or expired tokens. Explicit credentials still take precedence. Public-token helpers use server-side minting with run tokens rather than signing locally.
Project and organization queries, and branch overrides targeting another PREVIEW or DEVELOPMENT environment, keep using compatibility credentials. Branch headers do not change credential selection in STAGING or PRODUCTION. Chat subscriptions reread implicit credentials for each connection.
runs.subscribeToRunnow ends after the run completes. Thefor awaitloop exits right after the update with the final status, and the subscription stops its connection, so a script that subscribes to a run exits on its own. PassstopOnCompletion: falseto keep the subscription open after completion.Add
SupervisorHttpClient.releaseRun, which gives back a dequeued run the worker never started so the platform requeues it at once instead of after the pending execution timeout.The supervisor keeps its run notification subscriptions across reconnects to the webapp, and reconnects when the webapp turns its handshake away, so cancellations and resolved waits keep reaching running tasks after a webapp restart or deploy.
Asymmetric webhook sources can now verify ECDSA P-384 signatures (
algorithm: "ecdsa-p384", SHA-384) and providers that sign a SHA-256 digest of the signing string (prehash: "sha256"). ECDSA signatures are accepted in DER or rawr||sform.The bundled
trigger-cost-savingsskill now notes that a webhook delivery starts no run when no subscriber's filter matches, so it costs no compute.Stream a sub-agent's reply through a parent tool call with
chat.forwardSubAgent. Each chunk is written to the parent chat once and the tool resolves with the sub-agent's final message, so streaming a sub-agent costs bytes in proportion to its reply. Yieldingstream.messages()snapshots resends the whole message on every chunk, which grows with the square of the reply.execute: async ({ topic }, { toolCallId, abortSignal }) => { const stream = await researcher.sendMessage(topic, { abortSignal }); return await chat.forwardSubAgent(stream, { toolCallId }); },Render it while it runs with
useSubAgentMessages()from@trigger.dev/sdk/chat/react(orcreateSubAgentMessages()outside React).
Bug fixes
Fix
chat.injectmessages added from a tool mid-turn being saved before the assistant's response. They now stay after the tool result, where the model saw them, so the next turn keeps the same prompt prefix. If you roll@trigger.dev/sdkback to an earlier version, chats saved by this version lose these mid-turnchat.injectmessages from the model's context, though the chat history shown in the UI keeps them.Fix a
chat.agentturn failing after a head start that ended with two or more parallel tool calls. When those tools finished out of call order, the agent sent their results to the model twice on the next step, and the provider rejected the request (Anthropic: "each tool_use must have a single result"). Each handed-over tool result is now sent once.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Add "Ignored paths" to the Git settings: pushes and pull request updates that only change files matching these patterns no longer create a deployment. Ignored paths don't apply while the Vercel integration is connected.
The
metricsquery table now includes queue size (queue.size.*) and webhook limit metrics (webhook.waiters.*,webhook.processing.*,webhook.ingress.*), so you can chart and alert on queue capacity and webhook rate limits.New Limits alerts: watch the limits that can interrupt or degrade runtime flow, one at a time or combined into a single alert with "any" or "all" and the signals you choose (limit reached or approaching), in the dashboard, the API and the agent.
Expand short-lived run-token support to task APIs, with permission checks for packets, metadata, streams and waits. Run tokens last one hour independently of root-key rotation and cannot be individually revoked. They can mint public access tokens for up to 30 days; those tokens may outlive the run token that minted them.
Hosted webhook endpoints can verify ECDSA P-384 (SHA-384) signatures, ECDSA signatures in raw
r||sform, and RSA signatures made over a SHA-256 digest of the signing string (prehash: "sha256").Older runs now load their trace, span details and run events faster. A span that finishes more than a week after its run shows as still in progress.
The run page now loads large traces progressively and updates live runs incrementally, so big traces open faster and open run pages no longer reload the whole trace while a run is executing. The run trace API can also page large traces.
Query alerts now accept queries whose columns are computed from other aggregate columns, such as a percentage of two aggregates. When a query can't be watched, the Watch button stays visible but disabled and explains why.
Archiving unused queues from the Concurrency page is now available on all instances, including self-hosted.
Runs whose container or pod could not be created, or whose pod failed before the run started, can now be requeued straight away instead of waiting for the pending execution timeout. Both are off by default: set
RELEASE_UNSTARTED_RUNS_ENABLED=trueon a supervisor for creates that fail, andRELEASE_FAILED_POD_RUNS_ENABLED=truefor pods that fail.Session external ids can no longer contain a
/channelspath segment (for examplechat-1/channels/support) or end in:channels, since both forms name a session's channels. Creating a session with one now returns a 422 validation error.Selecting a span that started a session now shows a link to that session in the span panel, so you can jump from an orchestrator's run to its sub-agents.
Fix the batch results API returning an empty list of items for completed batches. It now returns every run's result in trigger order.
Fix the batch results API returning "Batch not found" for some batches that the batch retrieve API could see.
Fix the run page continuing to live-update forever for some cancelled runs. These runs now show as finished, and loading their trace is faster.
Fix fetching the trace of a child run through the API sometimes being very slow or failing. These requests now return quickly.
Run metadata changes sent with an attempt's completion, such as increments and appends, are no longer applied a second time when a completion that already went through is retried.
Changing your email address now requires clicking a confirmation button after opening the emailed link.
Fix intermittent read and subscription errors when multiple clients first open the same realtime stream.
Fix intermittent subscription failures and missed records when reading newly created realtime streams.
Fix the dashboard's task list and task filters occasionally going stale when several
trigger devsessions register at the same time.Deleting an organization now cancels its billing subscription.
Fix the dashboard agent's suggested threshold and window being dropped when it prefills a query alert.
Queries now reject an alias that reuses a table's alias in the same SELECT, unless the aliased expression contains an aggregate or window function (
count() AS runs FROM runsstill works).Queries using
WITH <expression> AS <name>now run instead of failing with a syntax error, and the name can be used in the rest of the query. The name can't reuse a table alias used anywhere in the query.Fix a rare case where clock skew between run engine instances could leave a run executing after its task finished, or stop a wait from ever resuming. A run's state changes are now always ordered in the order they happened, regardless of clock skew.
A run whose attempt start was interrupted no longer gets stuck executing without its task ever running, then failing as stalled.
Fixed dropdowns sometimes picking an option by themselves when typing with some on-screen keyboards or autofill.
New runs a session starts are now always linked to their session, so their Agent tab no longer fails to load because the link was missing.
Runs no longer lose their worker's token when the cluster answers the worker's create with a 408, so the worker starts instead of waiting for a requeue.
Runs no longer lose their worker's token when a concurrent delivery or a lost answer leaves a failed worker create's token behind: the worker that took the name keeps it, and a token nothing will use is cleaned up instead of being kept.
Deleting an organization now uninstalls its Vercel integration. A Vercel installation disabled on Vercel's side is reported as such instead of as an expired connection, and removing it no longer reports success.
Promoting or rolling back a deployment now updates your webhook endpoints to match the deployment that's now current.
All packages: v4.8.2
@trigger.dev/build, @trigger.dev/convex, @trigger.dev/core, @trigger.dev/linear, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, @trigger.dev/slack, trigger.dev
4.8.1
23 Oct 2026Fix
trigger deployfailing on self-hosted instances with custom base images. Stages built on a custom image now keep the trust store that image ships with.Alerts can now watch the result of any supported query: raise when a value crosses a threshold, when matching rows stop appearing, or when new matching rows appear. Create them from the Query page, the Dashboard Agent or the API, and see the alert's values charted on its page.
trigger.dev v4.8.1
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.8.1Release notes
Read the full release notes: trigger.dev/changelog/v4-8-1
Bug fixes
Fix
trigger deployfailing on self-hosted instances with custom base images. Stages built on a custom image now keep the trust store that image ships with.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Alerts can now watch the result of any supported query: raise when a value crosses a threshold, when matching rows stop appearing, or when new matching rows appear. Create them from the Query page, the Dashboard Agent or the API, and see the alert's values charted on its page.
All packages: v4.8.1
@trigger.dev/build, @trigger.dev/core, @trigger.dev/linear, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, @trigger.dev/slack, trigger.dev
4.8.0
23 Oct 2026Route verified webhooks into agent sessions with
chat.event({ endpoint, key }), and connect external chat surfaces withchat.channels.custom({ endpoint }). Both subscribe to a shared webhook endpoint, so an agent and your other webhook tasks can use the same provider URL. Channels support reply delivery, session binding, conversation seeding, and lifecycle reactions, and a failed turn posts a short line instead of the error (errorMessagesets it, as a string or a function of the failure). Usechat.createWatchToken()to watch a session from another surface.A connector can also stream replies natively (
stream()), mirror the session's state into the surface (lifecycle()), show tool calls as they run (progress()), stop a running turn from the surface (onControl()), post approvals and tool controls and resume the run from a verified click, download files only the surface can read (download()), and acknowledge or fold in messages that arrive mid-turn (received(),pendingMessages).Add hosted webhooks: declare an endpoint once with
webhooks.endpoint.define({ id, source })and Trigger.dev hosts its URL, verifies every request, and routes each event to the endpoint's subscribers. Subscribe tasks withwebhook({ endpoint, filter, onEvent }), each with its own type-safe filter, and pause a run until a matching webhook arrives withwebhooks.waiter.create()andwebhooks.waiter.wait().export const stripe = webhooks.endpoint.define({ id: "stripe", source: webhooks.stripe(), }); export const fulfill = webhook({ id: "fulfill", endpoint: stripe, filter: "event.type == 'checkout.session.completed'", onEvent: async ({ event }) => {}, }); const waiter = await webhooks.waiter.create(stripe, { match: { "event.data.object.metadata.orderId": order.id }, }); const { event } = await webhooks.waiter.wait(waiter).unwrap();Sources cover presets (
webhooks.stripe(),webhooks.github(),webhooks.svix(),webhooks.discord(), and others), named providers (webhooks.clerk(),webhooks.shopify(), and more) andwebhooks.custom<T>(config), and most carry a setup prompt an AI coding agent can follow to register the endpoint. Retries are deduplicated on the provider's own event or delivery id where it sends one. Filters, keys and waitermatchpaths share theevent.,header.andwebhook.namespaces, and filters accept== null/!= nullpresence checks andevent any (...)over a payload that is an array of events.webhook()takestask()options such asqueue,machineandretry. The HTTP API lists endpoints and deliveries, replays deliveries, and creates and cancels waiters, and both it and the MCP server can read an endpoint's setup prompt and generate or store its signing secret.The
generate_webhook_secretandset_webhook_secretMCP tools take an optionalpreviousSecretTtlSecondsto keep accepting a webhook endpoint's old signing secret while the provider switches to the new one (up to 7 days), and report when the old secret stops working.
trigger.dev v4.8.0
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.8.0Release notes
Read the full release notes: trigger.dev/changelog/v4-8-0
Improvements
Route verified webhooks into agent sessions with
chat.event({ endpoint, key }), and connect external chat surfaces withchat.channels.custom({ endpoint }). Both subscribe to a shared webhook endpoint, so an agent and your other webhook tasks can use the same provider URL. Channels support reply delivery, session binding, conversation seeding, and lifecycle reactions, and a failed turn posts a short line instead of the error (errorMessagesets it, as a string or a function of the failure). Usechat.createWatchToken()to watch a session from another surface.A connector can also stream replies natively (
stream()), mirror the session's state into the surface (lifecycle()), show tool calls as they run (progress()), stop a running turn from the surface (onControl()), post approvals and tool controls and resume the run from a verified click, download files only the surface can read (download()), and acknowledge or fold in messages that arrive mid-turn (received(),pendingMessages).Add hosted webhooks: declare an endpoint once with
webhooks.endpoint.define({ id, source })and Trigger.dev hosts its URL, verifies every request, and routes each event to the endpoint's subscribers. Subscribe tasks withwebhook({ endpoint, filter, onEvent }), each with its own type-safe filter, and pause a run until a matching webhook arrives withwebhooks.waiter.create()andwebhooks.waiter.wait().export const stripe = webhooks.endpoint.define({ id: "stripe", source: webhooks.stripe(), }); export const fulfill = webhook({ id: "fulfill", endpoint: stripe, filter: "event.type == 'checkout.session.completed'", onEvent: async ({ event }) => {}, }); const waiter = await webhooks.waiter.create(stripe, { match: { "event.data.object.metadata.orderId": order.id }, }); const { event } = await webhooks.waiter.wait(waiter).unwrap();Sources cover presets (
webhooks.stripe(),webhooks.github(),webhooks.svix(),webhooks.discord(), and others), named providers (webhooks.clerk(),webhooks.shopify(), and more) andwebhooks.custom<T>(config), and most carry a setup prompt an AI coding agent can follow to register the endpoint. Retries are deduplicated on the provider's own event or delivery id where it sends one. Filters, keys and waitermatchpaths share theevent.,header.andwebhook.namespaces, and filters accept== null/!= nullpresence checks andevent any (...)over a payload that is an array of events.webhook()takestask()options such asqueue,machineandretry. The HTTP API lists endpoints and deliveries, replays deliveries, and creates and cancels waiters, and both it and the MCP server can read an endpoint's setup prompt and generate or store its signing secret.The
generate_webhook_secretandset_webhook_secretMCP tools take an optionalpreviousSecretTtlSecondsto keep accepting a webhook endpoint's old signing secret while the provider switches to the new one (up to 7 days), and report when the old secret stops working.Realtime streams now reconnect and resume when the stream backend reports a failed read mid-stream, instead of ending early as if the stream had finished. This affects
runs.subscribeToRunwith streams,useRealtimeRunWithStreams, and chat streams.HMAC webhook verifier configs accept
additionalSignatureHeaders: more headers that can carry a signature, matched as alternatives tosignatureHeader. Providers that send a second signature during a secret rotation (Hookdeck'sx-hookdeck-signature-2) keep verifying through the rotation.Add
webhooks.hookdeck(), a source for deliveries relayed through a Hookdeck connection. It verifies thex-hookdeck-signatureheader with the project's signing secret, keeps verifying while the secret is being rolled (Hookdeck sends the previous secret's signature inx-hookdeck-signature-2), and deduplicates retries onx-hookdeck-eventid. The event is the original provider's payload, so pass its type:webhooks.hookdeck<Stripe.Event>(). If the Hookdeck project's header prefix was changed, pass it aswebhooks.hookdeck({ headerPrefix })so retries keep deduplicating.Add
@trigger.dev/linear: turn achat.agentinto a Linear agent. Assign it an issue or @mention it, and Linear's agent session becomes a durable Trigger.dev session: the reply posts back to Linear, tool calls show as activities,linearPlanTool()keeps the plan Linear shows as a checklist, and approvals are Approve and Deny options that resume the run.import { linear, webhookSource } from "@trigger.dev/linear"; const linearEvents = webhooks.endpoint.define({ id: "linear", source: webhookSource(), }); export const triage = chat.agent({ id: "triage", channels: [ linear({ id: "linear", endpoint: linearEvents, token: process.env.LINEAR_ACCESS_TOKEN!, }), ], run: async ({ messages, signal, streamText }) => streamText({ model, messages, abortSignal: signal }), });The first turn gets the issue's context and earlier comments, images and PDFs in the issue reach the model, a Stop in Linear winds the turn down, and
errorMessagesets the text a failed turn shows.Add
@trigger.dev/slack: turn achat.agentinto a native Slack agent. Each DM or channel thread is a durable session, the reply streams into the thread with the turn's tool calls shown as a plan, approvals are Approve and Deny buttons, and Slack's stop button stops the turn.import { appMentions, slack, webhookSource } from "@trigger.dev/slack"; const slackEvents = webhooks.endpoint.define({ id: "slack", source: webhookSource(), }); export const support = chat.agent({ id: "support", channels: [ slack({ id: "slack", endpoint: slackEvents, token: process.env.SLACK_BOT_TOKEN!, startOn: appMentions(), }), ], run: async ({ messages, signal, streamText }) => streamText({ model, messages, abortSignal: signal }), });startOndecides which channel messages start a session (appMentions()answers when the agent is @mentioned). Images and PDFs people share reach the model, messages sent while the agent is answering can be folded into the reply, tools can post their own buttons, andownWorkspaceOnlyignores Slack Connect guests.The
streamTextpassed to achat.agent'srun()now turns AI SDK telemetry on by default, so each model step and tool call shows up as a span in the run trace even when the agent doesn't store a prompt withchat.prompt.set(). An agent withtelemetry: { recordUserMessage: false }gets these spans without prompt and response content, including when it stores a prompt (whose variables are left out of the span metadata). Passexperimental_telemetry: { isEnabled: false }at the call site to turn them off, orrecordInputs: false/recordOutputs: falseto keep them without content.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
When regenerating an environment's API key you can now revoke the previous key immediately instead of keeping it working for 24 hours. Use this when a key may have leaked.
Set
KUBERNETES_POD_RESERVED_SOURCE_PORTSon the supervisor (for example50080,50081) to stop runs using those ports for outbound connections, which is useful to avoid port clashes.Rotating a webhook endpoint's signing secret can keep the old one valid for a while, so you can rotate without failing deliveries that are still signed with it. The rotate and regenerate dialogs let you choose how long the old secret stays valid (up to 7 days, 24 hours by default). The
rotate-secretandsecretendpoints accept an optionalpreviousSecretTtlSecondsand returnpreviousSecretExpiresAt. With no value, the old secret stops working immediately, as before.Alerts are now checked every minute instead of every 5–10 minutes, so they raise and recover sooner.
Run traces and trace APIs load faster for older runs.
The API keys page now always lists your root API key, masked to its last 4 characters when it's hidden, so you can regenerate it and revoke the previous key. When the root key is hidden, the page points you to creating an API key for your backend.
Runs whose deployment has no compute template now go to containers when they are triggered, instead of first passing through the compute worker queue.
Runs now get a
TRIGGER_DASHBOARD_URLenvironment variable with the dashboard's address, so a task can link to its run (${TRIGGER_DASHBOARD_URL}/runs/${ctx.run.id}) on any Trigger.dev instance. ATRIGGER_DASHBOARD_URLyou set on the project still wins.Creating an alert works without the dashboard agent.
Small fixes to creating and editing alerts.
Alerts sent to Slack channels connected through a removed Slack installation deliver again.
The supervisor no longer trusts certificates issued under the compromised emSign (eMudhra) certificate authorities.
All packages: v4.8.0
@trigger.dev/build, @trigger.dev/core, @trigger.dev/linear, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, @trigger.dev/slack, trigger.dev
4.7.7
22 Oct 2026- Security
Deployed tasks on the
node,node-22,node-24andnode-26runtimes now run on Node.js 22.23.4, 24.22.1 and 26.12.1, the October 2026 security releases. They fix CVE-2026-111497 (an out-of-bounds write in the Brotli decoder) and several TLS hostname verification bypasses. Existing deployments keep the old runtime until you redeploy with this version. - Security
Self-hosted: The webapp and supervisor images now run on Node.js 24.22.1. The supervisor no longer trusts certificates issued under the compromised emSign (eMudhra) certificate authorities, and the webapp image builds its database migration tool with Go 1.26.10, which rejects the compromised eMudhra intermediates.
This is a security release. Update the CLI and redeploy to pick up the fixes.
Security fixes
- Security
Deployed tasks on the
node,node-22,node-24andnode-26runtimes now run on Node.js 22.23.4, 24.22.1 and 26.12.1, the October 2026 security releases. They fix CVE-2026-111497 (an out-of-bounds write in the Brotli decoder) and several TLS hostname verification bypasses. Existing deployments keep the old runtime until you redeploy with this version. - Security
Self-hosted: The webapp and supervisor images now run on Node.js 24.22.1. The supervisor no longer trusts certificates issued under the compromised emSign (eMudhra) certificate authorities, and the webapp image builds its database migration tool with Go 1.26.10, which rejects the compromised eMudhra intermediates.
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Then redeploy your tasks with
npx trigger.dev@latest deploy.Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.7.7All packages are at v4.7.7: @trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.7.6
20 Oct 2026Added MCP tools for monitoring alerts:
list_alert_capabilities,list_alerts,create_alert, andresolve_alert, so an MCP client can discover what a project can watch and manage alerts directly. Health capabilities expose customizable threshold params, discoverable vialist_alert_capabilitiesand settable viacreate_alert.Deploy images no longer trust the emSign roots removed after the October 2026 eMudhra CA key compromise, or the Sectigo AAA root that cross-signs the compromised intermediates. Node and Bun tasks now refuse TLS connections through the compromised eMudhra intermediates, including their Sectigo AAA cross-signed copies.
NODE_EXTRA_CA_CERTSset as an environment variable now reaches the task process at startup instead of being overwritten by the image's empty default.
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.7.6Release notes
Read the full release notes: trigger.dev/changelog/v4-7-6
Highlights
Added MCP tools for monitoring alerts:
list_alert_capabilities,list_alerts,create_alert, andresolve_alert, so an MCP client can discover what a project can watch and manage alerts directly. Health capabilities expose customizable threshold params, discoverable vialist_alert_capabilitiesand settable viacreate_alert.
Improvements
Deploy images no longer trust the emSign roots removed after the October 2026 eMudhra CA key compromise, or the Sectigo AAA root that cross-signs the compromised intermediates. Node and Bun tasks now refuse TLS connections through the compromised eMudhra intermediates, including their Sectigo AAA cross-signed copies.
NODE_EXTRA_CA_CERTSset as an environment variable now reaches the task process at startup instead of being overwritten by the image's empty default.Python tasks and
pipin deploy images now verify TLS against the image's trust store instead of a pinned certifi bundle, so they also refuse the compromised eMudhra intermediates.
Bug fixes
Fix
timestampand otherDatefields being logged as{}in structured log lines.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Ask Trigger's message box is now a single panel holding your message, its context, New chat and Send, with a note that Ask Trigger is an AI assistant and can make mistakes. The chat header has a simpler layout menu and history list, and the Fullscreen layout is now called Full page.
The webapp Docker image no longer trusts the root certificates that chain to the compromised eMudhra intermediate CAs, so connections to servers presenting certificates from those intermediates now fail.
All packages: v4.7.6
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.7.5
20 Oct 2026Add
trigger.dev tasks trigger <task id>to trigger a task from your terminal. It uses the dev environment unless you pass--env, and--waitwaits for the run and prints its output or error, exiting with code 1 if it failed. Therunscommands now use the same dev branch astrigger devwhen you pass--env dev.npx trigger.dev@latest tasks trigger hello-world --payload '{"name":"Ada"}' --waitManage custom metric dashboards from code.
query.dashboardslists, creates, updates and deletes custom dashboards and their widgets, and every widget query is checked when it is saved. The MCP server addscreate_dashboardandset_dashboard_widgets, so your AI assistant can build a dashboard for you.import { query } from "@trigger.dev/sdk"; await query.dashboards.create({ title: "Email tasks", widgets: [ { title: "Total runs", query: "SELECT count() AS total FROM runs", display: { type: "bignumber", column: "total", aggregation: "sum" }, }, ], });trigger deployandtrigger promotenow say which environment they're targeting, and accept--prodas a shorthand for--env prod. WhenTRIGGER_ACCESS_TOKENholds an environment API key and you don't pass--env, they now use that key's environment instead of assuming prod. Passing an--envthat doesn't match the key is now an error, where before the deploy went to the key's environment.Preview deploys now detect the branch on CI providers that check out a detached HEAD, such as GitLab, Bitbucket, CircleCI, Buildkite, Travis CI, Jenkins and Azure Pipelines, instead of creating a branch called
HEAD. Test links printed after a preview deploy now open the preview branch you deployed instead of staging.The MCP
deploytool no longer defaults to prod, so your AI assistant has to choose the environment.
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.7.5Release notes
Read the full release notes: trigger.dev/changelog/v4-7-5
Improvements
Add
trigger.dev tasks trigger <task id>to trigger a task from your terminal. It uses the dev environment unless you pass--env, and--waitwaits for the run and prints its output or error, exiting with code 1 if it failed. Therunscommands now use the same dev branch astrigger devwhen you pass--env dev.npx trigger.dev@latest tasks trigger hello-world --payload '{"name":"Ada"}' --waitManage custom metric dashboards from code.
query.dashboardslists, creates, updates and deletes custom dashboards and their widgets, and every widget query is checked when it is saved. The MCP server addscreate_dashboardandset_dashboard_widgets, so your AI assistant can build a dashboard for you.import { query } from "@trigger.dev/sdk"; await query.dashboards.create({ title: "Email tasks", widgets: [ { title: "Total runs", query: "SELECT count() AS total FROM runs", display: { type: "bignumber", column: "total", aggregation: "sum" }, }, ], });trigger deployandtrigger promotenow say which environment they're targeting, and accept--prodas a shorthand for--env prod. WhenTRIGGER_ACCESS_TOKENholds an environment API key and you don't pass--env, they now use that key's environment instead of assuming prod. Passing an--envthat doesn't match the key is now an error, where before the deploy went to the key's environment.Preview deploys now detect the branch on CI providers that check out a detached HEAD, such as GitLab, Bitbucket, CircleCI, Buildkite, Travis CI, Jenkins and Azure Pipelines, instead of creating a branch called
HEAD. Test links printed after a preview deploy now open the preview branch you deployed instead of staging.The MCP
deploytool no longer defaults to prod, so your AI assistant has to choose the environment.trigger devworks better when a coding agent like Claude Code, Cursor or Codex runs it: it skips the install prompts, lists the tasks it registered, and prints each run's dashboard URL and output. For everyone, a failed build now ends with a line saying it will rebuild when you fix the errors, and retried attempts and crashed task processes now show their errors.Redact span content before it leaves the worker.
telemetry.spanProcessorsintrigger.config.tsruns your own span processors ahead of every export, to Trigger.dev and to your own exporters, so you can redact or drop span content before it reaches the run trace.chat.agentalso takes atelemetryoption to stop recording the user's message andclientDataon its spans.export default defineConfig({ telemetry: { spanProcessors: [new MyRedactingSpanProcessor()] }, }); chat.agent({ id: "my-chat", telemetry: { recordUserMessage: false, recordClientData: false }, run: async ({ messages, signal, streamText }) => streamText({ model, messages, abortSignal: signal }), });
Bug fixes
Fix run subscriptions crashing Node with
Controller is already closedafter youbreakout of the loop, and stop polling once you do.ApiClientsubscribe methods also accept a customfetchClient.
Other changes
Update the @modelcontextprotocol/sdk dependency to ^1.31.0.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Recent deployments made with
--local-bundlecan now be redeployed from the deployments list, rebuilding the same bundle with its build-time environment variables.The API keys page now prompts you to create your first key instead of showing an empty table.
The short link /_/billing now takes you straight to the billing page of your current organization.
A
batchTriggerAndWaitcould stay stuck executing after all of its child runs finished, if creating the batch was retried while the server was slow to respond. The parent now resumes with its child runs' results.The natural-language field on the schedule form returns a cron expression again instead of an error.
Fixed runs failing to resume from a wait when the platform had already resumed them but the confirmation was lost.
Run traces returned by the API no longer include internal debug events.
Fixed natural-language schedule generation in the schedule side panel.
A run whose process is killed is now only reported as out of memory when the machine actually ran out of memory. Any other kill (e.g. the machine being shut down or reclaimed) fails the attempt straight away as a crash, which is retried using your task's retry settings on the same machine size.
All packages: v4.7.5
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.7.4
14 Oct 2026Self-hosted instances can require custom deploy base images per runtime via the new
DEPLOY_BASE_IMAGESandDEPLOY_BUILD_BASE_IMAGESwebapp settings. The CLI builds on the images the instance specifies, and older CLIs are rejected with an upgrade message.Add a
replay_runtool to the MCP server, so your AI assistant can replay a run, optionally with a new payload, metadata, tags, machine, version, delay or other trigger options. It is hidden in--readonlymode.Override a concurrency limit's
perKeyfor a singleconcurrencyKey:concurrencyLimits.override(name, { concurrencyKey, perKey, ttl })caps that one key under that one limit for a while (7 days by default, 30 at most),reset(name, { concurrencyKey })clears it, andretrieve(name, { concurrencyKey })shows the key's bound and when the override expires.
trigger.dev v4.7.4
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.7.4Release notes
Read the full release notes: trigger.dev/changelog/v4-7-4
Improvements
Self-hosted instances can require custom deploy base images per runtime via the new
DEPLOY_BASE_IMAGESandDEPLOY_BUILD_BASE_IMAGESwebapp settings. The CLI builds on the images the instance specifies, and older CLIs are rejected with an upgrade message.Add a
replay_runtool to the MCP server, so your AI assistant can replay a run, optionally with a new payload, metadata, tags, machine, version, delay or other trigger options. It is hidden in--readonlymode.Override a concurrency limit's
perKeyfor a singleconcurrencyKey:concurrencyLimits.override(name, { concurrencyKey, perKey, ttl })caps that one key under that one limit for a while (7 days by default, 30 at most),reset(name, { concurrencyKey })clears it, andretrieve(name, { concurrencyKey })shows the key's bound and when the override expires.runs.replay()now takes options, so you can replay a run with a different payload, metadata, tags, queue, machine, version, delay and other trigger options. Anything you leave out comes from the original run, as before, and the payload is serialized liketrigger(), so values likeDateandBigIntkeep their types.import { runs } from "@trigger.dev/sdk"; await runs.replay("run_1234", { payload: { userId: "user_456" }, tags: ["replayed"], delay: "10m", });
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Self-hosted instances can add a Cloudflare Turnstile bot check to the magic-link sign-in form by setting
TURNSTILE_SITE_KEYandTURNSTILE_SECRET_KEY. It's off unless both are set.Recent deployments started from the GitHub integration or a native CLI deploy can be redeployed from the deployments list, rebuilding the same commit or upload as a new deployment.
Each webhook endpoint's request rate limit now comes from the organization's plan and can be raised per organization, and the limits page shows it.
Each environment's webhook endpoints now share a rate limit that counts larger request bodies as more than one request, set by the organization's plan and shown on the limits page.
Webhooks now appear in the dashboard side menu with a Beta badge, and organizations without access can request beta access from the Webhooks page. The New badges on Sessions, Prompts and Models are gone.
The new API key dialog's access summary now shows Errors, Webhooks and Waitpoints access, and API keys with waitpoint access can create, list and retrieve waitpoint tokens.
Log search uses whole-word matching for ASCII alphabetic terms, keeps substring matching for other terms, and incrementally searches older logs without blocking the page.
Magic links now only sign you in from the browser that requested them, so a link opened elsewhere (including by an email security scanner) no longer logs anyone in. Self-hosted instances can turn this off with
MAGIC_LINK_SAME_BROWSER_REQUIRED=false.The multi-factor authentication login page now focuses the code input, accepts pasted codes, and submits as soon as all six digits are entered.
Dashboard tabs left in the background now pause their live updates after 30 seconds and catch up as soon as you return, so idle tabs stop reloading data nobody is looking at.
Preview branch auto-archiving is now always available, with no feature flag to enable first.
Large run traces now load in chunks and update live without reloading the page, on child run pages as well as root runs.
The run page shows one clear trace status next to Cancel and Replay: whether the run is live, still loading, only partially shown, or failed to load (with a retry). Search, filters and the run actions now share a single full-width toolbar.
Keep blank Vercel imports from overwriting existing values when the default-off empty environment variable feature is enabled.
Errors on the login page, such as an expired or invalid magic link, no longer disappear a moment after the page loads in a new browser.
Magic-link sign-in emails now always link to
LOGIN_ORIGIN, whatever host the request came in on.Parent and root metadata updates from child tasks no longer stall behind a parent run that is being updated by many children at once, and can optionally be buffered in Redis so they survive a webapp restart.
Revoking a personal access token is now permanent. Logging in with the CLI again issues a new token instead of reinstating the revoked one, so you can rotate a leaked CLI token by revoking it and running
trigger logoutthentrigger login.Webhook deliveries from a provider's shared IP addresses are no longer throttled by other customers' traffic or by a spoofed
X-Forwarded-Forheader; the per-IP limit now applies only to requests for endpoints that don't exist, and every ingest 429 includesRetry-After.
All packages: v4.7.4
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.7.3
6 Oct 2026- Breaking
Creating or resuming a session with
POST /api/v1/sessionsnow requires both session-write and task-trigger permissions. Scoped keys and public tokens must grantwrite:sessions(or access to the target session) and permission to trigger its task. Update the minimatch dependency to ^10.2.3.
Add
trigger.dev orgs listto show the organizations you belong to, with their slugs and IDs. Use the slug withtrigger.dev projects create --org, including for organizations that don't have any projects yet.trigger.dev projects createnow activates the Free plan for organizations that don't have a plan yet, matchingtrigger.dev init.
trigger.dev v4.7.3
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.7.3Release notes
Read the full release notes: trigger.dev/changelog/v4-7-3
Breaking changes
- Breaking
Creating or resuming a session with
POST /api/v1/sessionsnow requires both session-write and task-trigger permissions. Scoped keys and public tokens must grantwrite:sessions(or access to the target session) and permission to trigger its task.
Improvements
Update the minimatch dependency to ^10.2.3.
Add
trigger.dev orgs listto show the organizations you belong to, with their slugs and IDs. Use the slug withtrigger.dev projects create --org, including for organizations that don't have any projects yet.trigger.dev projects createnow activates the Free plan for organizations that don't have a plan yet, matchingtrigger.dev init.Reports filed with the
submit_feedbackMCP tool now reach the Trigger.dev team. They were being sent, but not somewhere anyone was reading.Stopping a
chat.agentturn whoserun()returns astreamTextresult no longer sends anerrorchunk with "An unexpected error occurred". The turn ends quietly again and the run stays alive for the next message.chat.createStartSessionAction,chat.headStartandchat.startHeadStartnow accepttagsfor the Session itself, so chat sessions can be filtered by tag on the Sessions page.triggerConfig.tagsstill tags the session's runs.await startChatSession({ chatId, clientData, tags: [`org:${org.slug}`, `user:${user.id}`], });
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Self-hosted instances can block sign-in and sign-up from specific email domains with the new
BLOCKED_EMAIL_DOMAINSsetting.Run traces now appear almost immediately and load progressively as you watch, and much larger traces are viewable than before.
The Logs page loads and searches faster, and busy environments no longer fail to load it. Searches that are still too expensive now show a message suggesting a narrower range instead of a generic error.
Fix a rare case where a run could stay stuck executing after the child run or wait it was waiting on had completed.
Deployments with an unsupported
runtimenow fail with a 400 that names the supported runtimes, instead of a generic 500Preserve the cancellation reason when a run that was executing is finalized, instead of replacing it with the default text.
All packages: v4.7.3
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.7.2
2 Oct 2026Use the current Node.js LTS for deployments whose
runtimeis unset or set to"node". Set a versioned runtime such as"node-24"to keep deployments pinned to that Node.js major.chat.agentnow sends parallel tool results to the model in the order the tools were called, the same order the next turn's history uses. Models that bind their thinking to the exact conversation (Claude Sonnet 5.5, Claude Opus 5.5, Claude Fable 5.1) no longer lose a turn's reasoning, or fail the request on accounts that enforce the check, when its tools finish out of order.Recovering a long unfinished
chat.agentresponse on a continuation run no longer blocks the worker. Rebuilding the response from its streamed chunks now takes time linear in its length and yields to the event loop as it goes, so heartbeats keep firing and the run is not killed mid-replay. Capturing the response at the end of a long turn gets the same speedup.
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.7.2Release notes
Read the full release notes: trigger.dev/changelog/v4-7-2
Improvements
Use the current Node.js LTS for deployments whose
runtimeis unset or set to"node". Set a versioned runtime such as"node-24"to keep deployments pinned to that Node.js major.chat.agentnow sends parallel tool results to the model in the order the tools were called, the same order the next turn's history uses. Models that bind their thinking to the exact conversation (Claude Sonnet 5.5, Claude Opus 5.5, Claude Fable 5.1) no longer lose a turn's reasoning, or fail the request on accounts that enforce the check, when its tools finish out of order.Recovering a long unfinished
chat.agentresponse on a continuation run no longer blocks the worker. Rebuilding the response from its streamed chunks now takes time linear in its length and yields to the event loop as it goes, so heartbeats keep firing and the run is not killed mid-replay. Capturing the response at the end of a long turn gets the same speedup.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Fix the "Download payload" and "Download output" buttons for large payloads and outputs, which downloaded an error file instead of the data.
All packages: v4.7.2
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.7.1
2 Oct 2026trigger.dev initnow stops with a clear error when the target directory has nopackage.json, instead of installing packages into a parent project. A custom task directory entered during interactiveinit <path>is now written totrigger.config.tsrelative to the project directory.The CLI and MCP authorization page now shows the account and organizations you're granting access to.
trigger.dev v4.7.1
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.7.1Release notes
Read the full release notes: trigger.dev/changelog/v4-7-1
Improvements
trigger.dev initnow stops with a clear error when the target directory has nopackage.json, instead of installing packages into a parent project. A custom task directory entered during interactiveinit <path>is now written totrigger.config.tsrelative to the project directory.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
The CLI and MCP authorization page now shows the account and organizations you're granting access to.
All packages: v4.7.1
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.7.0
1 Oct 2026- Deprecated
Deprecate
queues.overrideConcurrencyLimitandqueues.resetConcurrencyLimit. These operate on the legacy model where a queue carried its own concurrency limit; declare concurrency with the taskconcurrencyoption and manage it withconcurrencyLimits.overrideandconcurrencyLimits.resetinstead. Chat agents can now scope concurrency per session. Pass
concurrencyKey(for example, your chat ID or tenant ID) and trigger-time named limits viatriggerConfig.concurrencywhen starting a chat session, fromchat.createStartSessionAction, theAgentChatclient, or a handover. Keys are never defaulted, so a session without one shares the task's keyless pool.const start = chat.createStartSessionAction("support-chat", { triggerConfig: { concurrencyKey: user.id }, });Concurrency limits can now be paused and resumed, just like queues:
concurrencyLimits.pause(name)stops every run holding the limit from being dequeued while keeping its configured bounds, andconcurrencyLimits.resume(name)starts them again.import { concurrencyLimits } from "@trigger.dev/sdk"; await concurrencyLimits.pause("openai"); await concurrencyLimits.resume("openai");
trigger.dev v4.7.0
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.7.0Release notes
Read the full release notes: trigger.dev/changelog/v4-7-0
Improvements
Chat agents can now scope concurrency per session. Pass
concurrencyKey(for example, your chat ID or tenant ID) and trigger-time named limits viatriggerConfig.concurrencywhen starting a chat session, fromchat.createStartSessionAction, theAgentChatclient, or a handover. Keys are never defaulted, so a session without one shares the task's keyless pool.const start = chat.createStartSessionAction("support-chat", { triggerConfig: { concurrencyKey: user.id }, });Concurrency limits can now be paused and resumed, just like queues:
concurrencyLimits.pause(name)stops every run holding the limit from being dequeued while keeping its configured bounds, andconcurrencyLimits.resume(name)starts them again.import { concurrencyLimits } from "@trigger.dev/sdk"; await concurrencyLimits.pause("openai"); await concurrencyLimits.resume("openai");Control a task's concurrency with the new
concurrencyoption, and share limits across tasks with named concurrency limits. An inline shape caps the task itself;concurrencyLimit()declares a limit any task can hold (up to two named limits per task), and a trigger call can switch a run's named limits with its ownconcurrencyoption.import { concurrencyLimit, task } from "@trigger.dev/sdk"; export const openaiLimit = concurrencyLimit({ name: "openai", total: 25 }); export const generateSummary = task({ id: "generate-summary", concurrency: [{ perKey: 1, total: 5 }, openaiLimit], run: async (payload) => {}, });perKeycaps eachconcurrencyKeypool andtotalcaps across everything, keys or not. The queue-levelconcurrencyLimitoption keeps working unchanged and is deprecated in favor ofconcurrency. Enforcement happens server-side; servers without support accept the option but do not enforce it yet.Manage limits at runtime with the new
concurrencyLimitsnamespace:list()andretrieve(name)report each limit's bounds plus its liverunningandqueuedcounts,override(name, { perKey, total })changes only the given bounds (overridingtotalto0pauses the limit), andreset(name)restores the declared values.Queue reads (
queues.list()andqueues.retrieve()) now report aversionthat discriminates the shape:V1queues keep today's fields (their ownconcurrencyLimitand its override state), whileV2queues (tasks declared withconcurrency) carry no queue-level concurrency, since their limits are read and overridden throughconcurrencyLimits(a task's inline limit under its derivedtask/<task-id>name). Existing reads keep compiling: aV2queue reportsconcurrencyLimitas null andconcurrencyas undefined.Chat streams now report
Stream stalled: no records receivedafter five retries of a connected stream that sends no records. Network failures and browser wakeups retain automatic recovery. Healthy tool calls with no records for about six minutes also reach this silence limit. Watch subscriptions remain unlimited, and caller cancellation still closes cleanly.Webhook verifier artifacts can now declare the provider's response contract as data: a handshake
respondStatus, the status codes returned for accepted deliveries and rejected signatures, and a GET verification flow (getHandshake) for providers that confirm a callback URL with a challenge. HMAC verifiers can read the timestamp from a body field, which the Linear provider config uses for its replay window, and the dashboard's test-send re-signs a recorded sample as of now so it passes that window.Add an optional
onSettledcallback toTriggerChatTransport.sendAction()so callers can confirm that their action's input was processed, independently of whether the response stream closes.Chat agents now return to a durable wait when a session wake does not deliver a matching message. This prevents resumed runs from staying active until their maximum duration and preserves the configured turn timeout across repeated wakes.
- Deprecated
Deprecate
queues.overrideConcurrencyLimitandqueues.resetConcurrencyLimit. These operate on the legacy model where a queue carried its own concurrency limit; declare concurrency with the taskconcurrencyoption and manage it withconcurrencyLimits.overrideandconcurrencyLimits.resetinstead. Steering messages now remain in context across agent steps and keep their original position in saved conversations, including custom response data written between steps.
Set up a new Trigger.dev account from the CLI. Login can prefill an email address, save the user's full name after authorization, and resume authorization later, while
initcan create the first organization, activate its Free plan, and create the first project before scaffolding the app.Added a
submit_feedbackMCP tool so coding agents can report a confusing tool error, a docs mismatch, or a missing capability without the user having to file it by hand. Turn it off with--skip-telemetryorTRIGGER_TELEMETRY_DISABLED; the tool is hidden while it is off.Authenticate
trigger promotewith environment API keys supplied throughTRIGGER_ACCESS_TOKEN. Environment API key commands now use the saved profile API URL when no explicit override is provided.Convert Zod 4
z.date()fields to date-time strings in JSON Schema without weakening validation for other unsupported types. This prevents MCP tool discovery from failing when a tool input schema contains a date.
Bug fixes
Fix stale and empty project environment values in
trigger dev, and support empty values insyncEnvVars().Fixes warm starts silently failing for deployments built with 4.6.0 to 4.6.3 in projects that resolve
zodto a 3.x release. The runner could not parse the run handed to it by the warm-start service and exited, leaving the run waiting until the platform redrove it a few minutes later and started it cold. Redeploy to pick up the fix.Fix a ~6-second delay between a task finishing and its run completing (and a ~31-second delay when cancelling a run) in projects that use zod 4.4 or newer. Run cost and billed usage was not impacted by this issue.
Fix Windows deploys failing at indexing with
Cannot find moduleon a percent-encoded path when the project directory contains spaces or non-ASCII characters.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
One concurrency key with a large backlog no longer holds up runs waiting on other keys on the same queue.
API rate limit usage is now recorded per environment in the
metricstable asapi.rate_limit.allowed,api.rate_limit.denied,api.rate_limit.remaining_minand the limit itself (api.rate_limit.limit.per_secondandapi.rate_limit.limit.burst), so you can chart requests against your limit and 429s over time on the Query page and dashboards.Archive queues you no longer use from the Concurrency page. Archived queues are hidden from the list and no longer count towards allocated concurrency.
Automatically archive preview branches after a configurable period without deployments, with protected branch names and a preview of affected branches.
Download a session’s original saved transcript file from the session inspector.
Organization Owners and Admins can now choose, in Settings under Support Access, whether Trigger.dev support can open their dashboard directly or only after an Owner or Admin approves a request, with each approval lasting 7 days.
Allocating extra concurrency to environments now requires billing permissions, the same as purchasing it. Allocation changes are also applied atomically, so simultaneous edits can no longer exceed your purchased concurrency.
Changing your account email address now sends a confirmation link to the new address; the change only takes effect once that link is opened. Requesting a magic link no longer creates an account until the link is used.
Removed the organization-wide Node.js 21 deprecation banner while keeping runtime upgrade guidance in Projects settings.
Creating a project now asks only for its name.
Prevent batch waits from remaining suspended when batch completion is briefly interrupted
Reject batch-and-wait requests when the parent run belongs to another environment
Keep dashboard pages visible during network interruptions, with a disconnected banner and a Refresh button instead of a full-page error.
Allow deployments to replace declarative schedules at the schedule limit when the resulting set stays within quota.
"Deploy now" now tells you when the branch doesn't exist on GitHub instead of showing a generic error, and a first deployment no longer flags a harmless build-cache message as an error.
Support empty-string environment values across the dashboard, API, and Vercel sync behind a feature flag, disabled by default.
Fixed a bug where a burst of telemetry could leave OpenTelemetry ingest rejecting every batch for a long time. Batches that wait too long are now dropped individually instead of restarting the processing workers, so ingest recovers as soon as the burst passes.
Keep scheduled task "Last run" times stable across unchanged deployments and align them with configured schedule windows.
Team members and pending invites on the organization Team page are now listed in alphabetical order.
All packages: v4.7.0
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.6.4
22 Sep 2026This release fixes a Zod import bug in 4.6.0 through 4.6.3 that could cause warm starts to fail and delay runs by approximately five minutes when using npm with Zod 3 pinned in
package.json. Cold starts were unaffected. Affected runs were automatically requeued. No data has been lost.trigger.dev v4.6.4
This release fixes a Zod import bug in 4.6.0 through 4.6.3 that could cause warm starts to fail and delay runs by approximately five minutes when using npm with Zod 3 pinned in
package.json. Cold starts were unaffected. Affected runs were automatically requeued. No data has been lost.Upgrade
Redeploy your tasks with the latest CLI:
npx trigger.dev@latest deploy
If you pin the CLI version, update it to 4.6.4 or later before redeploying. Existing deployments need a redeploy to receive the fix.
To update your project packages:
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.6.4Release notes
Read the full release notes: trigger.dev/changelog/v4-6-4
All packages: v4.6.4
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.6.3
17 Sep 2026Show how to override the default cron window in schedule policy warnings.
Thrown error
causechains are now captured and shown. When a task throws an error that wraps another one, the run's error in the dashboard, the CLI dev output, and failure alerts all carry the chain instead of only the outermost message.throw new Error("Could not sync the customer", { cause: originalError });The chain is flattened outermost first, capped at five causes, and cycle safe. It also rides on the
errorof API and realtime run records as acausesarray, andtriggerAndWaitandtriggerAndSubscriberebuild it as a nativecauseon the error they hand back, soerr.causeworks in your own catch blocks.Keep summarized assistant steps and tool results out of future
chat.agent()model context after inner compaction, while preserving the full visible conversation.
trigger.dev v4.6.3
Warning
A Zod import bug in versions 4.6.0 through 4.6.3 can cause warm starts to fail and delay runs by approximately five minutes when using npm with Zod 3 pinned in
package.json. Cold starts are unaffected by this bug. No data has been lost.Redeploy with
npx trigger.dev@latest deploy, or update your pinned CLI version to 4.6.4 or later and redeploy. Read about the fix.Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.6.3Release notes
Read the full release notes: trigger.dev/changelog/v4-6-3
Improvements
Show how to override the default cron window in schedule policy warnings.
Thrown error
causechains are now captured and shown. When a task throws an error that wraps another one, the run's error in the dashboard, the CLI dev output, and failure alerts all carry the chain instead of only the outermost message.throw new Error("Could not sync the customer", { cause: originalError });The chain is flattened outermost first, capped at five causes, and cycle safe. It also rides on the
errorof API and realtime run records as acausesarray, andtriggerAndWaitandtriggerAndSubscriberebuild it as a nativecauseon the error they hand back, soerr.causeworks in your own catch blocks.Keep summarized assistant steps and tool results out of future
chat.agent()model context after inner compaction, while preserving the full visible conversation.
All packages: v4.6.3
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.6.2
16 Sep 2026Authorize stored realtime payload and output downloads against their owning run. Large packet hydration continues to work for run-, task-, tag-, and batch-scoped public tokens without permitting arbitrary packet reads.
Show warm idle time and durable waits separately in chat agent traces. Durable waits now open the waitpoint inspector while waiting and after completion. Message span names are shorter, and repeated session IDs no longer crowd message-wait and default output-stream spans.
chat.agent: The between-turns compaction check now receives the last step's token usage (the context the model actually held) instead of the turn's sum over every tool-calling step, so a single tool-using turn no longer compacts a short conversation. The summed figure is still available as
turnUsageon the event. A head-start handover whose pending tool call completes under the same message id now replaces its spliced partial in the model lane directly instead of falling back to a full reconversion.
trigger.dev v4.6.2
Warning
A Zod import bug in versions 4.6.0 through 4.6.3 can cause warm starts to fail and delay runs by approximately five minutes when using npm with Zod 3 pinned in
package.json. Cold starts are unaffected by this bug. No data has been lost.Redeploy with
npx trigger.dev@latest deploy, or update your pinned CLI version to 4.6.4 or later and redeploy. Read about the fix.Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.6.2Release notes
Read the full release notes: trigger.dev/changelog/v4-6-2
Improvements
Authorize stored realtime payload and output downloads against their owning run. Large packet hydration continues to work for run-, task-, tag-, and batch-scoped public tokens without permitting arbitrary packet reads.
Show warm idle time and durable waits separately in chat agent traces. Durable waits now open the waitpoint inspector while waiting and after completion. Message span names are shorter, and repeated session IDs no longer crowd message-wait and default output-stream spans.
chat.agent: The between-turns compaction check now receives the last step's token usage (the context the model actually held) instead of the turn's sum over every tool-calling step, so a single tool-using turn no longer compacts a short conversation. The summed figure is still available as
turnUsageon the event. A head-start handover whose pending tool call completes under the same message id now replaces its spliced partial in the model lane directly instead of falling back to a full reconversion.Validate resource IDs when creating scoped public tokens. Explicitly empty IDs are now rejected instead of being interpreted as type-wide permissions.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
The banner that prompts you to set a billing limit now lets you choose to run without one, so you don't have to open your billing limit settings to dismiss it.
Org member invites now match emails case-insensitively, so an invite whose email casing differs from the invitee's account email can be accepted.
Limit public access tokens created through the JWT endpoint to the API key's permissions and a maximum 24-hour lifetime. Rotated environment keys can no longer create tokens during their grace period.
Realtime session writers now receive authorization limited to the requested session channel.
Prevent public session access tokens from authorizing durable chat snapshot uploads
All packages: v4.6.2
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.6.1
15 Sep 2026Show schedule policy warnings during development and deployment, and present Free plan schedule limits without internal stack traces.
New CLI commands:
projects create/get/rename,runs list/get/replay/cancel, andenv setWarn when a deployment uses the deprecated Node.js 21 runtime. Deployment logs now include upgrade guidance, and the account associated with the deployment receives an email notification.
trigger.dev v4.6.1
Warning
A Zod import bug in versions 4.6.0 through 4.6.3 can cause warm starts to fail and delay runs by approximately five minutes when using npm with Zod 3 pinned in
package.json. Cold starts are unaffected by this bug. No data has been lost.Redeploy with
npx trigger.dev@latest deploy, or update your pinned CLI version to 4.6.4 or later and redeploy. Read about the fix.Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.6.1Release notes
Read the full release notes: trigger.dev/changelog/v4-6-1
Improvements
Show schedule policy warnings during development and deployment, and present Free plan schedule limits without internal stack traces.
New CLI commands:
projects create/get/rename,runs list/get/replay/cancel, andenv setWarn when a deployment uses the deprecated Node.js 21 runtime. Deployment logs now include upgrade guidance, and the account associated with the deployment receives an email notification.
Bug fixes
Fix the MCP server failing every
tools/listcall with "Date cannot be represented in JSON Schema"
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
The assistant in the dashboard now answers with cards: investigation cards for run questions, carrying the run's timeline and links to the run, queue or deployment, alongside charts and tables you can open fullscreen or copy — including queue metrics — and it answers about another project or environment without you switching to it first. The assistant reads run timelines through a dedicated endpoint, so span durations and launch events are consistent on every event store; the public run trace API is unchanged.
Warn when Production projects still use Node.js 21 and link directly to update instructions
Deployments now show the runtime their worker actually reported, so Bun deployments are no longer labelled Node.js; a deployment with no recorded runtime shows a dash instead of a guess.
All packages: v4.6.1
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.6.0
14 Sep 2026- Breaking
Minimum supported Zod version is now
3.25.56released in June 2025. Trigger.dev now uses Zod 4 by default. Projects using Zod3.25.56or later 3.x releases remain supported. (#4039). Zod remains a runtime dependency of packages that execute schemas, so existing and new installations continue to receive it automatically. The matching peer dependency range allows package managers to reuse either a compatible Zod 3 or Zod 4 installation from your project. - Breaking
Reading a session's
.inchannel (GET /realtime/v1/sessions/{id}/inand/in/records) now requires a secret key. Public tokens, includingread:sessions:{id}, get a 403; they can still read.outand append to.in. A failed write to a realtime or chat session stream no longer crashes the process running it, and a dropped chat session output write is now logged instead of swallowed.
trigger.dev v4.6.0
Warning
A Zod import bug in versions 4.6.0 through 4.6.3 can cause warm starts to fail and delay runs by approximately five minutes when using npm with Zod 3 pinned in
package.json. Cold starts are unaffected by this bug. No data has been lost.Redeploy with
npx trigger.dev@latest deploy, or update your pinned CLI version to 4.6.4 or later and redeploy. Read about the fix.Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.6.0Release notes
Read the full release notes: trigger.dev/changelog/v4-6-0
Breaking changes
- Breaking
Minimum supported Zod version is now
3.25.56released in June 2025. Trigger.dev now uses Zod 4 by default. Projects using Zod3.25.56or later 3.x releases remain supported. (#4039). Zod remains a runtime dependency of packages that execute schemas, so existing and new installations continue to receive it automatically. The matching peer dependency range allows package managers to reuse either a compatible Zod 3 or Zod 4 installation from your project. - Breaking
Reading a session's
.inchannel (GET /realtime/v1/sessions/{id}/inand/in/records) now requires a secret key. Public tokens, includingread:sessions:{id}, get a 403; they can still read.outand append to.in.
Highlights
A failed write to a realtime or chat session stream no longer crashes the process running it, and a dropped chat session output write is now logged instead of swallowed.
Improvements
The
playwrightbuild extension now works with Playwright 1.58 and later. 1.58 changed theplaywright install --dry-runoutput, which made deploy image builds fail while downloading the browsers.Rename the dev error link to "Ask Trigger about this error"
Automatically archive up to three inactive development branches when creating a branch at the plan limit. Connected and recently active branches remain protected, and the CLI reports which branches were archived.
When the build log stream cannot be opened or disconnects during a build server deploy, the CLI now explains that the deployment itself is unaffected and exits immediately with a non-zero code, since it can no longer confirm the outcome. Previously a disconnect printed the raw stream error and left the process hanging.
Build logs no longer include docker's registry login output, most notably the credential-storage warning on failed builds.
Reduce sensitive values in CLI and SDK diagnostics, secure files created by
trigger env pull, and remove credentials from collected Git remote metadata.chat.agentpersists a conversation through aTranscriptStorage: an adapter withloadandsavethat the runtime drives after every turn, failed turn and history-changing action. The platform snapshot stays the default; bring your own to write the conversation to your database as it happens. Each save carries both the changes since the last one (so a row store writes only what changed, and an undo is onetruncateAfter) and the whole transcript as it now stands (so a document store writes it as-is with no state of its own).chat.agent({ id: "my-chat", storage: myTranscriptStorage, run: async ({ messages, signal, streamText }) => streamText({ model, messages, abortSignal: signal }), });chat.createLoadTranscriptAction(storage)anduseLoadTranscriptread the conversation back the same way for every storage, andrunTranscriptStorageTestsfrom@trigger.dev/sdk/ai/testchecks an implementation against the contract.Compaction summaries and
chat.injectcontext now survive a continuation run, and crash recovery runs for every agent, including one that owns its own context.hydrateMessagesis deprecated in favour ofloadContexton a storage. The snapshot format is now version 2, which older SDK versions cannot read.chat.agent: a run that recovers a session with more than one in-flight user message no longer drops the unanswered ones if it restarts mid-recovery. Recovered messages now hold the resume cursor until each has been answered, so a restart re-answers the rest instead of resuming past them. Previously the cursor could advance past messages that were only held in memory, so a crash before they were dispatched lost them.End a chat conversation from inside the agent with
chat.close({ reason }). The session row is closed, further sends are refused with HTTP 409, and the run exits without scheduling a continuation, so a budget cap, a completed goal, or a signed-out user can stop the conversation rather than only the current run.chat.agent({ id: "budgeted-agent", run: async ({ messages, signal }) => streamText({ model: openai("gpt-4o"), messages, abortSignal: signal }), onBeforeTurnComplete: async ({ chatId }) => { if (await overBudget(chatId)) { chat.close({ reason: "Monthly budget reached" }); } }, });The current turn still streams in full. Decide the close before the turn ends (
run(),prepareStep,onBeforeTurnComplete) so the closed state rides out on that turn's final record and the user sees it as soon as the answer finishes.TriggerChatTransportpicks the close up from the response stream or from a refused send, exposes it astransport.sessionStatus(chatId)plustransport.sessionClosedReason(chatId), and stops sending and reconnecting. Closing a session from outside withsessions.close()now also reaches a live run, so an idle or suspended agent exits on its next wake instead of waiting out its idle timeout. Writes to a closed session's named side channels are refused with the same 409.Reading a page of a chat agent's conversation no longer downloads the whole conversation. The saved transcript now carries an index, so asking for the most recent messages fetches only those messages, and history loads in roughly constant time however long the chat gets.
A paged read also returns only the conversation itself. The model-side context an agent keeps, its compacted history and any injected context, is no longer included, so it cannot reach a browser through a load-transcript server action.
The built-in storage is deliberately basic about long conversations: once an agent has compacted, it keeps roughly the last hundred messages and drops the rest, so what it rewrites each turn stops growing. A conversation that never compacts is kept whole. If your app renders history further back than that, give the agent your own transcript storage.
The saved format has changed and an older SDK cannot read it, so a deployment rolled back to an earlier version will not find a readable transcript for conversations the newer version already saved, and those conversations continue from the live stream tail instead. Roll forward rather than back, or keep your own transcript storage.
Adds the
GetDeploymentArtifactUrlResponseBodyschema for the deployment artifact download URL endpoint.Deployments now return the
--external-idthey were deployed under asexternalId, and a run can read its own fromctx.deployment.externalId. Also fixes the deployments list failing when one deployment had no git metadata.Add an optional
appliedSchedulePolicyfield to the schedule API response. It is present only when a non-overridable plan policy applies a minimum window to a schedule (e.g. a free-plan schedule's minimum run interval); the configuredwindowcontinues to be returned separately and unchanged.Triggering a task whose id cannot be represented in a URL (for example an id containing an unpaired surrogate) now fails with a clear error naming the task id, instead of a cryptic URI error.
Actions can now become turns.
onActionedits history withchat.history; to answer after the edit, returnchat.turn()and a turn runs on the edited history with everything a turn has: the agent's system prompt and tools, steering, compaction, injected instructions,onTurnStartandonTurnComplete, and persistence. A regenerate ischat.history.slice(0, -1); return chat.turn();.onAction: async ({ action }) => { if (action.type === "regenerate") { chat.history.slice(0, -1); return chat.turn(); } if (action.type === "undo") chat.history.slice(0, -2); // edit only },Returning a
StreamTextResult,stringorUIMessagefromonActionis no longer supported and now fails with an error pointing tochat.turn(). A response produced that way skipped every turn guarantee, and its delivery to the browser was unreliable: the frontend never read the streamtransport.sendActionreturned, so a regenerate that appeared to work on the server did not render.History edits made by an action are still persisted as before: platform-managed snapshots are written after the edit, and apps with their own store mirror the edit themselves.
run()now receives astreamTextwith your agent's managed options already applied, so they cannot be lost by leaving out the spread:run: async ({ messages, signal, streamText }) => streamText({ model, messages, abortSignal: signal });Spreading
chat.toStreamTextOptions()still works and is equivalent. The difference is what happens when your options collide with the managed ones. Passingtoolsafter the spread replaces the skill tools, and passing your ownprepareStepreplaces the managed one, which silently switches off steering, compaction and injected context. The managedstreamTextmerges tools and composesprepareStepinstead, so neither can be turned off by accident.systemcan be set at the call site, onchat.agent({ system }), or throughchat.prompt.set(), but only in one of them: setting it in two places throws, because no single shape merges two system values across every supported AI SDK version, and dropping one silently is the failure this seam exists to prevent. Injected instructions append to whichever one is in play.chat.agent()also takesregistry,cacheControlandsystemProviderOptionsnow, so a managed prompt's model and its cache breakpoint no longer have to be passed at the call site.chat.toStreamTextOptions()applies them as well, so spreading it into thestreamTextimported fromaistays equivalent to the onerun()receives.chat.headStartandchat.startHeadStarthand theirrunthe same thing, carrying the options the handover protocol depends on. There it matters more: re-settingmessages,prompt,stopWhenorabortSignalafter a spread breaks the handover rather than degrading a feature, and nothing caught it. On the managed one those four keys are a type error;toolsis yours to pass.Actions are sent through
useChatso a turn that follows one renders like any turn.TriggerChatTransportrecognisesbody.actionon auseChatrequest and sends it as an action, sosendMessage(undefined, { body: { action } })orregenerate({ body: { action } })sends the action anduseChatowns the response: it streams into the message list,statusanderrorbehave as for a message, andstopworks.useChatActions({ sendMessage })in@trigger.dev/sdk/chat/reactis a two-line convenience over that.const { sendMessage } = useChat({ id: chatId, transport }); const { sendAction } = useChatActions({ sendMessage }); sendAction({ type: "regenerate" });Previously the frontend docs said
useChatconsumed the streamtransport.sendActionreturns; it never did, so an action's answer was never rendered by an app following them.transport.sendActionstill returns a stream that callers outsideuseChatmust read, and now accepts{ abortSignal, metadata }, with per-action metadata merged over the transport'sclientData.Chat sessions can now be pinned to a deployment, so a conversation keeps talking to the agent version its release shipped with, and follows the pin on its own when your app redeploys. Opt out with
triggerConfig: { externalDeploymentId: null }orversionSkew: "hold". Also fixesAgentChatignoringmaxDuration,regionandlockToVersion, and a restoredAgentChatsession never picking up a new deployment id.chat.agent: achat.historyedit made inonTurnCompleteafter a failed turn is now kept. Previously the edit was applied only when the turn succeeded, so a failure record or a card the hook closed on the error path never reached the transcript.chat.agent: after a Head Start turn whose handed-over tool call was followed by more tool steps, the next turn no longer fails withtool_use ids must be unique. The runtime kept the warm step's pending tool call in the model context alongside the completed response that already contained it.chat.agent: a continuation boot no longer re-dispatches the message that resumed it, and a turn with no new user message no longer calls the model. Previously a resumed run could answer the same message twice, and the second attempt failed against providers that reject a trailing assistant message, overwriting an answer that had already completed.useTriggerChatTransportnow picks up changes toaccessToken,startSessionandfetchon re-render, so a chat that stays mounted while the surrounding page changes no longer keeps sending to the endpoint captured on first render.Steering messages are now kept in the conversation when you drive turns yourself with
chat.createSession()orchat.MessageAccumulator. Previously a message that arrived mid-answer shaped that answer and then existed nowhere: it was missing fromturn.uiMessages, so an app persisting from there never stored it, missing fromturn.messages, so every later turn answered as though it had never been sent, and it was not queued as its own turn either. It now lands in both, the same way it does onchat.agent.Injected system context is merged into a single instruction block, so it works on every supported AI SDK version. Note that a cached system prompt gives up its cache entry for as long as an injection is live, since the cached prefix has changed.
chat.inject()withrole: "system"now works. It previously put the system message into the conversation, which AI SDK 7 rejects for every provider: the next turn died with a generic "An error occurred." and persisted an empty assistant message, so the agent looked like it had stopped answering. System-role context is now appended to the model's instructions, which is also the only way to inject context the agent treats as trusted.Two things to know. Instructions are delivered by
chat.toStreamTextOptions(), so arun()that callsstreamTextwithout spreading it does not receive a system-role injection. The conversational lane has no such requirement. And an injection applies to the next turn only, rather than repeating on every turn that follows it. Every inference call in that turn sees it, so arun()that builds options more than once gets the same instructions each time. An instruction injected after an action has run, and before the next message, reaches that next turn rather than the one after it.Undo, edit and regenerate now survive a run ending. History rolled back from
onActionwas only kept in the running worker's memory, so the rollback held while that worker stayed warm and then reverted on the next continuation. The undone messages came back, minutes later, with no error. This also holds when the turn before the action failed: the rollback used to be written against the cursor from before that turn, so a continuation could replay output the failed turn had already superseded.Server-side
AgentChatstreams now reconnect when the connection drops mid-turn instead of ending with a truncated reply, and a turn that still cannot be resumed ends with an error rather than a silent truncation.Session public tokens can now be narrowed to one stream:
read: { sessions: "chat_123:out" }grants read access to that session's.outchannel only, without access to the session record or its other channels.Steering messages injected mid-answer are now part of the conversation, both for your hooks and for the model on later turns. Previously they reached the model for the answer they steered and reached the browser, but nothing else:
onTurnCompletenever saw them, so an app storing its own transcript lost the instruction the answer was shaped by, and it vanished from the conversation on reload. The model also forgot the instruction from the next turn onwards, answering as though the message had never been sent, while the chat UI still showed it. This holds when the steered turn fails part-way, and whenpendingMessages.preparereshapes the message: later turns now see the same form the steered turn did, not the original message.Approving a tool call no longer undoes compaction. A tool-approval continuation used to rebuild the model's context from the full conversation, so a chat that had been summarised to fit the context window was sent the whole transcript again on the next call, and could go over the limit it had just been compacted to avoid.
If you worked around this by saving steering messages as they arrive, in
pendingMessages.onReceivedfor example, that write now duplicates the one you get fromnewUIMessages. Drop it, or skip messages you have already stored.Reloading a chat while the agent is still answering now shows the message being answered. Previously the incoming message was only persisted once the turn finished, so a refresh mid-answer showed the reply arriving with no question above it.
Adds
chat.deferBeforeOutput()for app-owned writes that the next page load has to see. Likechat.defer()the work is not awaited by the hook that registers it, so it runs alongside the model and costs no time to first token, but the answer is held until it lands. Use it for the conversation or message write you previously had toawaitinonTurnStart, as long as nothing else in the turn reads that write back: it orders the write against what the frontend can see, not against the model, so a tool that reads the same row still needs an awaited write.Chat.agent transcript fixes: a turn that errors before the model produces any content no longer stores an empty assistant message, an error thrown without a message now shows a generic error instead of a blank one, and a custom transcript storage no longer needs to preserve exact message JSON for a compaction to survive a continuation.
Bug fixes
Fixes storage of large trigger payloads for task ids containing a slash, which could fail the trigger with an "Invalid packet storage path" error. It affected ids that started or ended with a slash, contained two slashes in a row, or contained a
.or..path component. The storage path is now built from a generated id rather than from the task id, so no task id can produce an unusable one, and payloads that are already stored are still read from where they were written.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Projects that need a Node.js runtime update can now be handed to a coding agent: the organization Projects settings page has a button that copies a ready-to-paste prompt listing every project to update.
Additional API keys are now enabled by default. New environments no longer display root API keys, and existing environments can permanently disable their visibility
New schedules use a default CRON spread window when none is set, distributing runs after their scheduled time instead of starting them all at once. Set an explicit window to override the default.
Schedules now support a configurable minimum spread window that applies even when a smaller window is requested.
The "Cancel in-progress runs when this limit is reached" option on the billing limit form is now enabled by default when you first configure a limit, so already-executing runs stop instead of continuing past the limit. Organizations that have already saved a billing limit keep their existing choice.
Creating and archiving Development and Preview branches now requires the branch management permission, which the Developer role has by default.
The assistant in the dashboard no longer has a monthly message limit, so you can chat with it as much as you like.
Asking it to keep an eye on something and tell you when it happens is rolling out gradually, so it isn't offered in every organization yet.
Ask Trigger now opens as a floating window you can drag anywhere and resize, and the chat header lets you switch it to a right-side panel or fullscreen. Choose the position it opens in from your account settings.
The Queues page Allocated tile now explains that it is the sum of your queue concurrency limits, and no longer shows a warning color when those add up to more than the environment limit, which is expected.
Deleting a project now stops its pending runs. Runs that were waiting on a
delayor sitting in the queue are cancelled instead of executing later, and a deleted project no longer sends task failure alerts.Fixes an intermittent "Invalid access token" failure caused by the deployment log stream token expiring while a deploy was still in flight.
Dashboard pages no longer keep polling for updates while their browser tab is hidden, which could leave a tab you came back to showing a connection error instead of your data. Pages refresh when you return to the tab.
Stop counting agent LLM calls twice. An agent framework emits a wrapper span around the inference span that did the work, and both were priced, so LLM cost aggregates and the AI metrics page reported roughly double for agent workloads. Per-call figures in the run view were always correct and are unchanged.
Retried trigger and batch trigger requests are deduplicated again: when the SDK automatically retries a request that the server had in fact already accepted, you get the original run or batch back instead of a duplicate one.
Fix the Queues page showing "No activity" on the queue-metrics charts for some organizations even though their metrics were being collected. Those charts now display the collected data.
The queue page's "Oldest wait" card now shows a single clear number (how long the oldest waiting run has been waiting) with an explanatory tooltip, and no longer shows a second "worst" figure that could confusingly read lower than the headline.
Run replication now recovers on its own after a Redis restart or outage, in place of logging "Cannot extend an already-expired lock" and holding the replication slot open until the server is restarted. Deployments running under a process supervisor can set
RUN_REPLICATION_MAX_RESUBSCRIBE_ATTEMPTSto exit and be restarted when a stream cannot recover.Reject waitpoint registrations that target a run outside the authenticated environment
Switching environments now keeps you on the current page when a task's id contains a slash, instead of dropping you back to the list. The test page for a webhook task whose id contains a slash also opens correctly now.
GitHub App installations are now linked only after the installing GitHub user authorizes the App and is verified to have access to the installation.
All packages: v4.6.0
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.5.16
2 Sep 2026The
trigger.dev deployandtrigger.dev devcommands now warn (with the suggested fix) when your code loads a package throughcreateRequire()that won't be available in the deployed image. Previously it would fail at runtime in production to load the package. Deploys also now show bundler warnings for your code instead of discarding them.Fixes an issue introduced in 4.5.11 that made deploy image builds of projects with large dependency trees noticeably slower.
A durable guard improves reliability for runs waiting on triggerAndWait or batchTriggerAndWait if there's a database error that interrupts a child run finishing.
trigger.dev v4.5.16
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.5.16Release notes
Read the full release notes: trigger.dev/changelog/v4-5-16
Improvements
The
trigger.dev deployandtrigger.dev devcommands now warn (with the suggested fix) when your code loads a package throughcreateRequire()that won't be available in the deployed image. Previously it would fail at runtime in production to load the package. Deploys also now show bundler warnings for your code instead of discarding them.
Bug fixes
Fixes an issue introduced in 4.5.11 that made deploy image builds of projects with large dependency trees noticeably slower.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
A durable guard improves reliability for runs waiting on triggerAndWait or batchTriggerAndWait if there's a database error that interrupts a child run finishing.
All packages: v4.5.16
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.5.15
31 Aug 2026Stop shipping compiled test files in the published packages. The
*.test.tssources were being emitted intodist, adding dead weight to every install and leaving modules thatrequire("vitest")(not a dependency) inside the tarball, which tripped tooling that walks every file in a package.Named side channels on a Session: durable, two-way realtime streams that outlive a single run and are shared across runs. Open a channel with
sessions.open(id).channel(name)(orchat.channel(name)inside achat.agent) to get an.in/.outpair addressed by name rather than the reserved default pair. Writing a side channel's.indoes not wake or trigger a run, so a channel can carry out-of-band data (a stream of frames, a control signal) that many clients read while the agent produces it.// Inside a chat.agent: stream frames on a named channel, wakes nothing const frames = chat.channel("screenshots"); await frames.out.append(frame); frames.in.on((control) => { /* client control, no suspend */ });Declare channel record types once with
sessions.defineChannel(...)and infer them on both the producer and the consumer, includinguseSessionStreamChannelin React. Channels get a default retention that keeps them bounded, overridable per channel.Session
triggerConfig.tagsnow accepts up to 10 tags, matching the run tag limit. Previously it was capped at 5, which forchat.agentleft room for only 4 of your own tags after the automaticchat:{chatId}tag.
trigger.dev v4.5.15
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.5.15Release notes
Read the full release notes: trigger.dev/changelog/v4-5-15
Improvements
Stop shipping compiled test files in the published packages. The
*.test.tssources were being emitted intodist, adding dead weight to every install and leaving modules thatrequire("vitest")(not a dependency) inside the tarball, which tripped tooling that walks every file in a package.Named side channels on a Session: durable, two-way realtime streams that outlive a single run and are shared across runs. Open a channel with
sessions.open(id).channel(name)(orchat.channel(name)inside achat.agent) to get an.in/.outpair addressed by name rather than the reserved default pair. Writing a side channel's.indoes not wake or trigger a run, so a channel can carry out-of-band data (a stream of frames, a control signal) that many clients read while the agent produces it.// Inside a chat.agent: stream frames on a named channel, wakes nothing const frames = chat.channel("screenshots"); await frames.out.append(frame); frames.in.on((control) => { /* client control, no suspend */ });Declare channel record types once with
sessions.defineChannel(...)and infer them on both the producer and the consumer, includinguseSessionStreamChannelin React. Channels get a default retention that keeps them bounded, overridable per channel.Session
triggerConfig.tagsnow accepts up to 10 tags, matching the run tag limit. Previously it was capped at 5, which forchat.agentleft room for only 4 of your own tags after the automaticchat:{chatId}tag.
All packages: v4.5.15
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.5.14
28 Aug 2026Native build server deploys now show a single updating build log line by default; pass
--build-logs fullto stream every line (always used in CI and when output is not a terminal).Realtime stream subscriptions can now refresh an expired access token and reconnect, via a new optional
refreshAccessTokenoption on the client configuration and the React hooks.Subscribe to a realtime stream from its latest record instead of replaying the whole history. Pass
from: "latest"touseRealtimeStream,streams.read(), orfetchStreamto start at the current tail (the latest record, then live updates) instead of replaying (a live "last value" view), andmaxPartsto keep the accumulatedpartsarray bounded. A reconnect or remount resumes from the last record it saw, so no records are missed and none are replayed.from: "latest"needs a server that supports it; older servers safely fall back to a full replay.useRealtimeStreamalso gains alastEventIdoption and returns thelastEventIdof the last part seen, so you can persist the cursor (for example across a page reload) and resume exactly where you left off. AnonPartscallback delivers each throttled batch of parts with their event ids.const { parts, lastEventId } = useRealtimeStream<Frame>(runId, "frames", { from: "latest", // skip history, start at the current tail maxParts: 1, // keep only the most recent frame lastEventId: savedCursor, // resume from a persisted cursor onParts: (batch) => save(batch.at(-1)?.id), // track the cursor accessToken, });
trigger.dev v4.5.14
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.5.14Release notes
Read the full release notes: trigger.dev/changelog/v4-5-14
Improvements
Native build server deploys now show a single updating build log line by default; pass
--build-logs fullto stream every line (always used in CI and when output is not a terminal).Realtime stream subscriptions can now refresh an expired access token and reconnect, via a new optional
refreshAccessTokenoption on the client configuration and the React hooks.Subscribe to a realtime stream from its latest record instead of replaying the whole history. Pass
from: "latest"touseRealtimeStream,streams.read(), orfetchStreamto start at the current tail (the latest record, then live updates) instead of replaying (a live "last value" view), andmaxPartsto keep the accumulatedpartsarray bounded. A reconnect or remount resumes from the last record it saw, so no records are missed and none are replayed.from: "latest"needs a server that supports it; older servers safely fall back to a full replay.useRealtimeStreamalso gains alastEventIdoption and returns thelastEventIdof the last part seen, so you can persist the cursor (for example across a page reload) and resume exactly where you left off. AnonPartscallback delivers each throttled batch of parts with their event ids.const { parts, lastEventId } = useRealtimeStream<Frame>(runId, "frames", { from: "latest", // skip history, start at the current tail maxParts: 1, // keep only the most recent frame lastEventId: savedCursor, // resume from a persisted cursor onParts: (batch) => save(batch.at(-1)?.id), // track the cursor accessToken, });Added a
useSessionStreamReact hook for reading a session's output or input channel in realtime. It accumulates records with automatic resume from the last record you received, and supportsfrom: "latest"(start at the current tail, only new records after you connect),maxRecords(keep a bounded number of records in memory), alastEventIdresume cursor, and anonRecordscallback that delivers each throttled batch of records with their event ids.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Task retries that wait in the queue no longer count against the queue's internal redelivery limit, so runs with many long-delay retries are not wrongly failed with TASK_RUN_DEQUEUED_MAX_RETRIES.
All packages: v4.5.14
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.5.13
28 Aug 2026- Deprecated
New Vercel connections now get version skew protection turned on automatically, so each run uses the task version its deployment shipped with. Automatic atomic deployments are deprecated and no longer offered when you connect a project, but stay available in your Vercel integration settings.
trigger.dev deploynow asks the server whether to build with Depot or the native build server unless--native-build,--depot-build, or--local-buildis passed, so the native build server can be rolled out per organization without a CLI change.--local-bundleand--detachnow require--native-build.Add an experimental
--local-bundledeploy flag that runs the install and bundling steps on your machine and uploads only the build output; the image is still built remotely. Useful when your project's install step needs tooling or credentials that only exist locally.
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.5.13Release notes
Read the full release notes: trigger.dev/changelog/v4-5-13
Improvements
trigger.dev deploynow asks the server whether to build with Depot or the native build server unless--native-build,--depot-build, or--local-buildis passed, so the native build server can be rolled out per organization without a CLI change.--local-bundleand--detachnow require--native-build.Add an experimental
--local-bundledeploy flag that runs the install and bundling steps on your machine and uploads only the build output; the image is still built remotely. Useful when your project's install step needs tooling or credentials that only exist locally.Send the CLI version header on all API requests so deployments are attributable to a CLI version
A message that arrives mid-turn and is not injected into that turn is now answered as the next turn, instead of being dropped. This is what the
pendingMessagesdocs have always described, and it applies to the default too: configuringpendingMessageswithout ashouldInjectdeclines every batch, which previously meant every mid-turn message was lost with no error at either end.chat.agent({ id: "my-chat", pendingMessages: { onReceived: ({ message }) => logger.info("arrived mid-turn", { id: message.id }), // Only interrupt once the agent has started calling tools. shouldInject: ({ steps }) => steps.length > 0, }, run: async ({ messages, signal }) => streamText({ model, messages, abortSignal: signal, // Required for injection. Without it nothing injects, and every // mid-turn message is answered as the next turn instead. ...chat.toStreamTextOptions(), }), });A declined message keeps its place in the queue, so it survives a crash and is answered by whichever run picks the conversation up. An injected one is consumed at the moment it is injected, so it is never also answered as a later turn.
Browser chats now keep the active turn open across page reloads when older completion records are replayed.
Add
chat.endAndContinue()so fully hand-rolled custom chat agents can hand a conversation off to a fresh run on the latest deployed task version while preserving unconsumed Session input.Custom chat agents now validate and parse client data declared with
chat.withClientData({ schema })before passing it to agent code.
Bug fixes
Fixes a case where a chat could silently lose a message. If a message arrived while the agent was between turns and a stop arrived after it, the cursor the next boot resumed from could point past that message, so it was never answered and no error was raised. This affected
chat.agent, not just custom agents.Fixes a recovered answer being cut off. After a crash the agent replays the message it had not answered yet, but it was replaying the stop that arrived after that message too, so the turn answering it was aborted the moment it began. A stop is now only applied to the turn that was live when it arrived. That holds however the stop got there: sent after the last completed turn, or sent to a chat whose most recent turn was completed by an older version of the SDK.
One limitation to know about: the recovered answer is persisted correctly, but a chat page that stayed open across the crash keeps showing the partial answer it had already received. Reload the page to see the full recovered answer.
Also fixes a retried send being answered twice. When a send was retried and its idempotency claim was lost, the agent could consume the same message a second time.
Custom agent loops can now inspect pending chat input without consuming it, and consume one record at a time, with
chat.messages.hasPending()andchat.messages.next(). Records carry stable identifiers so a redelivery is recognisable.if (await chat.messages.hasPending()) { const record = await chat.messages.next({ timeoutInSeconds: 0 }); if (record) handle(record.payload); }hasPending()answers for messages alone, so a message sitting behind a stop, or behind a record this version of the SDK does not recognise, still reports as pending and is still delivered. Anything the agent has no consumer for is discarded rather than left where it would make every message queued behind it undeliverable.chat.messages.next()returningundefinedmeans no message became consumable before the timeout.chat.writeTurnComplete()'ssessionInEventIdis the cursor that is safe to resume from, not the sequence of the record the turn answered. It is held back behind any message still waiting to be handled, so a value below the record you just handled is expected.Fixed a chat agent hanging after an interrupted turn: when a run was killed mid-answer (out of memory, crash, or eviction) and only the one message it was answering was still outstanding, the new run never replied to it. That message is now re-answered on the new run.
Fix chat transport discarding the next turn after stopping generation.
skipToTurnCompleteis now reset when a new message or action is sent, so a message sent afterstopGenerationstreams normally instead of leaving the chat stuck in a streaming state.Fixes a message sent while the agent was mid-answer being lost if the run then crashed. The cursor written at the end of each turn could point past a message that had arrived during that turn but had not been answered yet, so the next boot skipped it and no error was raised anywhere. Such a message is now held until a turn actually takes it.
This also removes the in-memory buffer those messages used to sit in, on both
chat.agentandchat.createSession(), so a message waiting for its turn is durable rather than only present in the worker that received it.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Self-hosted instances can now disable the admin dashboard and user impersonation entirely. See the self-hosting docs for the new setting.
The dashboard has two new themes, Black and White, plus appearance options for stronger colors and underlined links.
Deployment logs no longer jump to the bottom while you are reading earlier output. Scroll up to pause auto-scroll, and scroll back down or use the new scroll-to-bottom button in the log header to resume following.
Customize the runs list: show, hide, and reorder columns, and add smart columns that pull a value straight out of a run's payload, metadata, or output. Your column choices are saved in the page URL, so you can share a view, bookmark it, or save it straight to your favorites.
Stop the browser offering to autofill or save environment variable values as saved credentials.
Cut webapp CPU usage by about a quarter on the routes that workers call most, freeing headroom at the same request rate. Detailed event-loop blocking traces are no longer recorded by default, because producing them was itself a large part of that cost.
When a runs list or runs.list API request spans too much data to complete, it now returns a clear, actionable error asking you to narrow the time range, instead of failing with a generic error.
Improved the performance and reliability of the runs list and the runs.list API, especially for large projects and filtered views.
- Deprecated
New Vercel connections now get version skew protection turned on automatically, so each run uses the task version its deployment shipped with. Automatic atomic deployments are deprecated and no longer offered when you connect a project, but stay available in your Vercel integration settings.
The Staging branch setting now shows an upgrade prompt on plans that don't include a Staging environment, instead of looking editable and then silently doing nothing when saved.
All packages: v4.5.13
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.5.12
20 Aug 2026Define stable execution windows on declarative scheduled tasks. Schedule API responses now expose both the nominal CRON time and its assigned time, while the dashboard shows configured windows and upcoming assignments.
trigger.dev deploy --external-idtags a deployment with an id of your own — a commit SHA, a CI run id, a release tag — so runs triggered by that release of your app go to that deployment. Deploying an id that is already deployed builds nothing and reports the existing version instead of creating a duplicate; use--forceto rebuild it.List the current Production runtime for every accessible project with
trigger projects list. Add--needs-updateto identify projects currently running Node.js 21.
trigger.dev v4.5.12
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.5.12Release notes
Read the full release notes: trigger.dev/changelog/v4-5-12
Highlights
Define stable execution windows on declarative scheduled tasks. Schedule API responses now expose both the nominal CRON time and its assigned time, while the dashboard shows configured windows and upcoming assignments.
Improvements
trigger.dev deploy --external-idtags a deployment with an id of your own — a commit SHA, a CI run id, a release tag — so runs triggered by that release of your app go to that deployment. Deploying an id that is already deployed builds nothing and reports the existing version instead of creating a duplicate; use--forceto rebuild it.List the current Production runtime for every accessible project with
trigger projects list. Add--needs-updateto identify projects currently running Node.js 21.New projects created with
trigger inituse Node.js 24 by default. Deployments without explicitruntimenow use their project's configured default runtime.Deployment builds now use custom base layer images and no longer install system packages during every build. This improves layer caching resulting in both faster deployments and faster image pulls on the worker cluster side.
Unrelated runs are no longer merged into a single trace in your external observability tool when they happen to execute on the same warm worker process.
Task metrics no longer go missing for projects that configure their own
metricExportersormetricReaders, and the flush error that came with it is gone.idempotencyKeys.reset()now works when your idempotency key is itself 64 characters long (for example if you use a hash of your own as the key). Previously any 64-character key was assumed to be already hashed, so passing one along with ascopesilently ignored the scope and the reset never found a matching run. Keys returned byidempotencyKeys.create()continue to be reset exactly as before.Pin runs to the deployment your calling code came from, so an old release never triggers tasks from a new one: set
TRIGGER_EXTERNAL_DEPLOYMENT_IDto the id you deployed with, orTRIGGER_AUTOMATIC_SKEW_VERSION_PROTECTION=1to detect the commit automatically on Vercel and most CI systems. Runs triggered before that deployment finishes building wait for it, then start pinned.Fair queue tenants can no longer get permanently stuck behind leaked concurrency slots. Slots are now freed on every path that finishes a message, a failed release no longer causes a message to run twice or lose its retry, and a background sweep frees any slot that does leak, so a tenant's queues recover on their own instead of needing manual cleanup.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Deployments and runs now show the external ID they were deployed or pinned with, so you can trace a run back to the release of your app that triggered it.
Operators can now route an organization's runs to specific Kubernetes node pools.
Dashboard pages load faster on projects with many preview branches by no longer loading every environment on each page.
Global log search now supports faster bounded substring matching and clearer time-range expansion.
Triggering tasks is now more resilient to brief, transient service interruptions, so short stalls are less likely to surface as errors.
Failed AI SDK tool call and embedding spans now show the error message and stack trace in the run inspector, below the tool input.
Archiving a branch now returns you to the same page of the branches list, keeping your place, search and filters instead of resetting to the first page.
Using
*as a concurrency key no longer stops a queue from being processed. Triggering a single run with that key could leave the whole queue stalled, including runs using other concurrency keys on it, until something else was triggered on the same queue.Fixed a brief window after promoting or rolling back a deployment where newly triggered runs could still execute on the previous version. New runs now pick up the current version immediately.
Root API keys no longer show an environment creation timestamp as their creation date.
The app version shown on the organization settings page now reports the real version instead of v0.0.0.
Fix paused environments starting to run work again after a deploy: a paused environment now stays paused until you resume it.
Reject alert webhook destinations in reserved benchmarking IP ranges.
TRQL queries using the PREWHERE clause are now rejected with a clear error message. Use WHERE instead, which is filtered the same way but keeps your data isolation guarantees intact.
Run trace rows now respond consistently to mouse and keyboard selection, including Alt-click expansion controls.
The "Back to app" button in organization settings now returns you to that organization instead of your most recently used one.
Runs triggered with a
ttlcould get permanently stuck in the queued state if they started executing and were then requeued after a failure (for example a worker dying mid-run) once the TTL had already elapsed. Requeued runs now dequeue normally: a run's TTL only applies while it is waiting to start for the first time.
All packages: v4.5.12
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.5.11
13 Aug 2026Allow
trigger deployto authenticate with an environment API key fromTRIGGER_ACCESS_TOKEN.Chat in the browser now reconnects when the connection drops mid-turn, instead of leaving the reply stuck as if it were still generating. Reports can be fetched as structured data with the
jsonformat, and the shortest report period is now one minute (1m,30m,1h,7d). Themint-tokencommand's help is clearer too: a token minted without--capis read-only, and--ttlshows the correct maximum lifetime of 7 days.The dev environment onboarding now tracks real progress. After you run
init, the setup checklist marks your project as initialized, and it updates live as your dev server connects and your tasks register. The blank state also adds a "Copy AI agent prompt" button that copies a ready-to-paste setup prompt (pre-filled with your project reference) for Claude Code, Cursor, or any coding agent.The
initscaffold now imports from@trigger.dev/sdkinstead of the deprecated@trigger.dev/sdk/v3subpath.
trigger.dev v4.5.11
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.5.11Release notes
Read the full release notes: trigger.dev/changelog/v4-5-11
Highlights
Allow
trigger deployto authenticate with an environment API key fromTRIGGER_ACCESS_TOKEN.
Improvements
Chat in the browser now reconnects when the connection drops mid-turn, instead of leaving the reply stuck as if it were still generating. Reports can be fetched as structured data with the
jsonformat, and the shortest report period is now one minute (1m,30m,1h,7d). Themint-tokencommand's help is clearer too: a token minted without--capis read-only, and--ttlshows the correct maximum lifetime of 7 days.The dev environment onboarding now tracks real progress. After you run
init, the setup checklist marks your project as initialized, and it updates live as your dev server connects and your tasks register. The blank state also adds a "Copy AI agent prompt" button that copies a ready-to-paste setup prompt (pre-filled with your project reference) for Claude Code, Cursor, or any coding agent.The
initscaffold now imports from@trigger.dev/sdkinstead of the deprecated@trigger.dev/sdk/v3subpath.Deployed images now ship dependencies and bundled task code as separate layers. Repeat deploys with unchanged dependencies typically push and pull far less data, making deploys and worker image pulls faster.
The current-worker API now reports each task's queue, so you can see which tasks write to a given queue.
Watch-mode chat streams now survive quiet windows and page reloads, and a reply cut off by a lost connection shows an error instead of appearing finished. Aborting a resumed subscription only closes your local stream — call
stopGeneration(chatId)or passstopOnAbort: trueto stop the run. Also fixed a race where quickly restarting a stream could break stop and reconnect, and stopping a chat now hands it back to your other tabs instead of leaving them read-only.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
The dashboard agent now has a monthly message allowance and plan-based limits on watches. Queries stay read-only with clearer errors when busy, and messages with unusual characters no longer fail to send.
Meet the dashboard agent: a chat in every environment that answers questions about your runs, queues, errors and health with real data and links, replacing Ask AI everywhere it used to appear. Investigate a failed run, an error, a backed-up queue or a run that hasn't started to get a worked-through answer — what happened, why, and how to fix it, with every claim linked to the runs, errors and deploys behind it. It reads your data read-only, works on preview and dev branches with that branch's own data, and reads the same everywhere — dashboard, terminal, editor. A very long chat keeps working: the agent summarises the earlier part and carries on.
Watch… on a run, queue, error or the health report tells you when things change: a run finishes, a queue clears or grows past a number you pick, an error comes back, an environment recovers. The answer arrives in the chat and, if you want, by email, Slack or webhook — and the agent can look into bad news on its own. A watch reaches you on any browser you sign in from, without opening the chat first.
A sample of conversations is scored automatically so the agent keeps getting better; only the score and a one-line summary are kept, never your messages, data or code, and we can switch it off for your organization on request. Ask the agent instead of the Docs buttons in page headers — they stay there when the agent isn't available to you. Separately, a queue's wait times, peak depth, throughput and throttling can now be read from the API.
Add backend support for delaying cron schedules within a specified window with a minimum of 60 seconds.
Reduced recurring background database load from the billing-limit recovery check, so paused environments are reconciled with less overhead.
Validating a schedule when deploying or updating a schedule now does less work on projects with many preview branches, so those operations stay fast as branches accumulate.
Project pages now load faster for projects with a large number of preview branches, by no longer loading archived branch environments that aren't shown.
Database queries that filter on a list of values now reuse cached query plans more consistently, instead of forcing the database to re-plan whenever the list length changes.
Routine cleanup of old dashboard agent data now runs on its own schedule.
Database connection metrics are now reported for every configured database connection instead of only the primary one, and stay accurate regardless of connection type.
Deployment-related API endpoints now draw from their own generous rate limit budget, configurable via the
DEPLOYMENT_RATE_LIMIT_*environment variables, so runtime API traffic no longer competes with deployments for the same per-environment budget.Deleting or editing a secret environment variable is now fast and no longer slows down as a project accumulates variables.
Speed up personal access token lookups by indexing them on their owner
Switching project or organization in the sidebar now keeps you on the same page instead of sending you back to Tasks. Pages for a specific run, deploy or other single item open the matching list instead.
Reduced database load when loading the dashboard by removing an unused organization member count that was being calculated on every page navigation.
The environment variables page now loads a page at a time, keeping it fast for projects with a large number of variables. Search matches variable names across every page.
Groundwork for an alternative database connection driver, gated behind configuration and disabled by default, so there is no change to default behavior.
Deleting an alert channel is now fast and no longer slows down as a project builds up alert history.
Reduced internal overhead on the API under high load.
Out-of-date upgrade prompts no longer appear in the dashboard: the "V4" badges and the notices saying preview branches and the queues table need V4 have been removed. The side menu still warns you when a project is on v3, with updated wording and a link to the v4 upgrade guide.
Make background worker registration cheaper for projects with many scheduled tasks by scoping declarative schedule reconciliation to the current environment and dropping redundant schedule lookups.
Speed up setting and importing environment variables for projects with many variables.
Loading the deployments list is now faster, especially when filtering by deployment status on projects with many deployments.
Fixed the billing limits page timing out for organizations with many preview branches, especially while a spend limit was being enforced. The page now loads quickly, so you can raise or resolve your limit without delay.
Fix the Concurrency page showing the plan's default concurrency for the dev environment instead of the environment's actual limit.
Creating an organization sometimes left you back on the creation form even though the organization had already been created, so clicking Create again made a duplicate. Creating an organization now completes and takes you to your new organization.
Ensure creating a project completes instead of returning to its creation form after a navigation error.
Renaming a project now keeps you on the project settings page and tells you what happened, instead of silently moving you to the tasks page or clearing the form with no explanation.
Fixed support threads showing no account details for some customers, so the team can see your plan, organizations and projects when you get in touch.
In the light theme, the Format, Clear and Copy buttons on the query editor no longer blend into the query text behind them.
The health report now says start latency is "unknown" when there is no data for it, instead of showing a healthy-looking 0ms
Realtime streams written inside a chat session run now use the same backend as the session itself, and runs are no longer created against a backend that cannot serve them.
The grouped "watch updates" notification now shows the total number of results waiting, instead of only the most recent batch's count.
All packages: v4.5.11
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.5.10
7 Aug 2026Allow task-scoped environment API keys to run batch operations for their permitted tasks. The SDK declares the batch's task set before creation, and
@trigger.dev/core/v3/apiKeysnow exports the additional-key format helper.Refresh package builds for TypeScript 7 compatibility while preserving existing runtime entry points. Projects using
emitDecoratorMetadata()with TypeScript 7 can install the@typescript/typescript6compatibility package alongside it; the package remains optional, so installing the Trigger.dev CLI does not install an additional compiler.AgentChat.reconnect()now settles promptly when reconnecting to an idle chat instead of holding the connection open for the full long-poll window. Also upgrades the S2 streamstore client to 0.25 and moves realtime streams to S2's current hosts.
trigger.dev v4.5.10
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.5.10Release notes
Read the full release notes: trigger.dev/changelog/v4-5-10
Highlights
Allow task-scoped environment API keys to run batch operations for their permitted tasks. The SDK declares the batch's task set before creation, and
@trigger.dev/core/v3/apiKeysnow exports the additional-key format helper.
Improvements
Refresh package builds for TypeScript 7 compatibility while preserving existing runtime entry points. Projects using
emitDecoratorMetadata()with TypeScript 7 can install the@typescript/typescript6compatibility package alongside it; the package remains optional, so installing the Trigger.dev CLI does not install an additional compiler.AgentChat.reconnect()now settles promptly when reconnecting to an idle chat instead of holding the connection open for the full long-poll window. Also upgrades the S2 streamstore client to 0.25 and moves realtime streams to S2's current hosts.You can now choose the region a run executes in when triggering a task through the MCP server.
Transient connection errors when a run starts are now retried for longer, so a brief connectivity blip no longer sends the run back through the queue and delays its first attempt.
debouncenow works when you pass an array of items tobatchTriggerorbatchTriggerAndWait, and when you trigger fromuseTaskTrigger. Previously the option was accepted by the types and dropped before the request was sent, so every trigger created its own run instead of collapsing onto the debounce key.await myTask.batchTrigger([ { payload: { id: "a" }, options: { debounce: { key: "same-key", delay: "30s" } }, }, { payload: { id: "b" }, options: { debounce: { key: "same-key", delay: "30s" } }, }, ]);The streaming (async iterable) forms of the batch calls were already forwarding
debouncecorrectly.
Bug fixes
Fix a chunk occasionally dropped when a chat.agent run takes over from the warm first turn. The realtime stream writer now reports the inclusive last-written position as the resume cursor, so the agent's first record after the handover is no longer skipped.
Fix a preloaded
chat.agentrun dropping an in-flight message when it retries after an out-of-memory error. The message being processed when the run hit the OOM is now recovered and re-run on the retry, instead of being skipped while the run waited for a new message.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Self-hosted deployments can now create multiple full-access API keys for each environment.
Short links like /_/apikeys now take you straight to that page in your current project and environment, so you no longer need the full URL with your org, project and environment in it.
The dashboard gets a refreshed Dark theme as its new default look. On the account page you can switch to Light, System preference (follows your OS), or the original Classic look, and fine-tune the new themes with a contrast slider.
Additional environment API keys can now create scoped public access tokens.
Additional environment API keys can authenticate API requests using their configured permissions, with revoked and expired keys rejected. Batch responses use server-issued public access tokens so additional keys never need the environment signing secret.
Self-hosted Kubernetes deployments can now add tolerations to run pods, so runs are allowed onto tainted nodes. An invalid toleration now stops the supervisor at startup instead of failing every run pod, so check existing values before upgrading.
Lower background database load during deployments and dev sessions for projects that use declarative schedules.
Triggering a task now does one fewer database write, so runs reach the queue slightly faster.
Creating or updating a schedule, and deploying a project with declarative schedules, is faster in long-lived projects with many deploys.
Admins opening an impersonation link from outside the dashboard now get a confirmation page naming the organization and destination instead of being bounced back, and while impersonating they can switch to "View as user" to see the dashboard exactly as that user sees it, with the admin-only UI and the impersonation highlight both hidden. Stopping impersonation is still one click away in the account menu.
Browser tabs now name the page you're on, and the run, task or queue when you're looking at one, instead of all reading "Trigger.dev".
Allow the database connection pool and connect timeouts to be tuned separately for each database's writer and read replica, falling back to the shared defaults when unset.
In-app feedback and add-on/quota requests are now recorded with more account context for the support team.
Self-hosted Kubernetes deployments now measure running-task count more accurately when deciding whether to pause pulling new work, so the safeguard engages closer to its configured thresholds.
The Queues pages now open on the last hour instead of the last day, and remember the time period you picked when you navigate between queues or reload the page.
Speeds up resolving the latest worker version and deployment for an environment, removing an occasional stall when triggering runs in projects that have accumulated many deployed versions.
API rate limits now apply per environment, so creating extra API keys no longer increases how many requests an environment can make.
When the capacity signal drops out, the last decision is held for a grace period rather than released.
Batch triggers no longer fail to start their runs when an environment is under heavy API load. If a batch still can't finish being created,
batchTriggerAndWaitnow fails with an error instead of leaving the parent run waiting forever, and the batches page says so rather than reporting that it resumed.Triggering a run with a very large
priorityno longer fails. The priority is now capped to the highest supported value instead of erroring out.Fix debounce doing nothing when the delay was longer than an hour, which made every trigger
create its own run instead of collapsing onto the debounce key. Debounced runs now keep being
pushed back for as long as triggers keep arriving, so setmaxDelaywhen the work has to happen
eventually, and settings that could never debounce are rejected rather than silently ignored.Honor the configured database connection timeout so brief connection spikes no longer surface as spurious "can't reach database server" errors.
Fixed a rare case where a single run or span carrying data that could not be ingested would make other runs or trace events in the same batch go missing from the runs list, traces, and logs. Now the rest of the batch is always kept: an affected run still appears with its status (only its un-ingestable output is dropped), and an affected trace event or payload is skipped instead of taking down everything around it.
Fix the sidebar "Help & Feedback → Contact us" form sometimes not sending your message. It now sends reliably every time.
Requests spanning multiple tasks now require permission for every requested task instead of accepting permission for only one task.
The four charts at the top of the Queues page now always cover the whole environment, so paging through or re-sorting your queues no longer changes them. The scheduling delay chart also leaves a gap where no runs started, instead of dropping to zero.
Reject alert webhook destinations in reserved benchmarking IP ranges.
Fix the health report failing with an internal error when requested through the API.
Triggering a task no longer intermittently fails to create the run when a database write briefly stalls.
Team members who join an organization through single sign-on or directory sync now get their own development environment for every project, so the dashboard's dev view and
trigger devbecome available to them without an admin having to set anything up. Members who were already missing one are repaired the next time their membership is synced from your identity provider.Fixed a rare error where triggering a task could fail if the idempotency key or debounce key contained an invalid null character. The character is now removed automatically and the run is created as normal.
All packages: v4.5.10
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.5.9
30 Jul 2026- Breaking
Setting a queue concurrency limit higher than your environment limit is now rejected with an error instead of being silently reduced to the environment limit, so a queue never looks like it has more capacity than it can get. Limits already saved are unchanged.
trigger mcpnow always starts the MCP server, and the interactive install wizard has moved behindtrigger mcp --install. Previously the wizard opened whenever stdout was a terminal, so any MCP host that spawns the command over a pseudo-terminal waited on a server that never started and eventually timed out.Ask whether an environment is healthy and get an answer instead of a wall of charts.
trigger report healthreturns a verdict on three questions: is work flowing, are the runs that start succeeding, and is the telemetry fresh enough to trust either answer. When something looks wrong it names the most likely cause and a next action.npx trigger.dev@latest report health --env prod --period 24h
The verdict is computed server side, so the CLI, the new
get_reportMCP tool, andGET /api/v1/reports/healthall return the same text with the same sparklines. In MCP hosts that support prompts,reportis also available as a slash command.
trigger.dev v4.5.9
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.5.9Release notes
Read the full release notes: trigger.dev/changelog/v4-5-9
Breaking changes
- Breaking
Setting a queue concurrency limit higher than your environment limit is now rejected with an error instead of being silently reduced to the environment limit, so a queue never looks like it has more capacity than it can get. Limits already saved are unchanged.
Improvements
trigger mcpnow always starts the MCP server, and the interactive install wizard has moved behindtrigger mcp --install. Previously the wizard opened whenever stdout was a terminal, so any MCP host that spawns the command over a pseudo-terminal waited on a server that never started and eventually timed out.Ask whether an environment is healthy and get an answer instead of a wall of charts.
trigger report healthreturns a verdict on three questions: is work flowing, are the runs that start succeeding, and is the telemetry fresh enough to trust either answer. When something looks wrong it names the most likely cause and a next action.npx trigger.dev@latest report health --env prod --period 24h
The verdict is computed server side, so the CLI, the new
get_reportMCP tool, andGET /api/v1/reports/healthall return the same text with the same sparklines. In MCP hosts that support prompts,reportis also available as a slash command.Prevent build debug logs from including environment variable values.
Send the running CLI version when checking for platform notifications so notices can be limited to compatible CLI releases.
Correct the
expirationTimedocs onauth.createPublicTokenand the trigger-token helpers: a number is a Unix timestamp in seconds, not milliseconds.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
A queue's concurrency limit can now be set as a percentage of your environment limit, from the dashboard or the API. Percentage limits track the environment limit, so raising or lowering it re-divides capacity without you editing every queue.
See how every queue in an environment is doing: backlog, throughput, concurrency against its limit, when it was throttled, and how long runs waited before starting. Each queue also gets its own page, which breaks the same numbers down per concurrency key so you can tell whether one key is starving the rest.
The agent detail page now uses the same layout as the other metrics pages: filters stay pinned at the top, the activity charts sit in a row beneath them, and the tabs and table scroll with the page, with the agent config in a resizable panel on the right.
Self-hosted instances can now serve deployed runs' API traffic from a different origin than the public one, per organization, via the
INTERNAL_API_ORIGINenvironment variable and a feature flag.A queue's concurrency keys are now paged and searchable, so a queue with thousands of keys shows all of them instead of only the busiest 50.
Accepting an old invitation could change the role of someone who was already in the organization. An invitation now leaves an existing member's role untouched, people who are already in an organization are no longer sent invitations to it, and the invite form now says which addresses it skipped instead of failing with an unhelpful error.
Removed an unused internal dashboard sync route that is no longer part of any product surface.
Fixed error reports being attributed to the wrong request when several requests were in flight at once.
Invalid queries sent to the query API are no longer treated as internal errors, and a query that does fail is now recorded together with the query text that produced it.
All packages: v4.5.9
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.5.8
27 Jul 2026Preserve the partial assistant message when a chat turn's model stream fails mid-response.
chat.agentnow passes the recovered partial toonTurnComplete, andchat.createSession'sturn.complete()keeps it before rethrowing, instead of dropping the streamed-so-far output.Favorite any dashboard page to a new Favorites section in the side menu, and customize the sidebar by renaming favorites, hiding items, and reordering items and sections.
List API endpoints now clamp the page size to a maximum of 100. Requests asking for a larger page size return up to 100 items and keep paginating, rather than pulling an unbounded page.
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.5.8Release notes
Read the full release notes: trigger.dev/changelog/v4-5-8
Improvements
Preserve the partial assistant message when a chat turn's model stream fails mid-response.
chat.agentnow passes the recovered partial toonTurnComplete, andchat.createSession'sturn.complete()keeps it before rethrowing, instead of dropping the streamed-so-far output.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Favorite any dashboard page to a new Favorites section in the side menu, and customize the sidebar by renaming favorites, hiding items, and reordering items and sections.
List API endpoints now clamp the page size to a maximum of 100. Requests asking for a larger page size return up to 100 items and keep paginating, rather than pulling an unbounded page.
Organizations without billing alerts now get default spend alert thresholds, so you're notified before usage grows unexpectedly. The billing limit page no longer pre-selects an option before you've set a limit and prompts you to configure one. Alert previews now update immediately after you change your billing limit.
When you create a Personal Access Token, the generated token now shows its first and last few characters instead of being fully hidden, so you can confirm you copied the right value.
Add metrics to the realtime backend that measure how often a single changed run is served to multiple subscriptions in one batch.
Realtime run subscriptions can now be configured to read run data straight from the primary database, so a run's latest state is never served from a lagging replica. Off by default; replica reads are unchanged unless you turn it on.
SSO and Directory Sync are no longer restricted to Enterprise plans — get in touch and we can turn them on for your organization whatever plan you're on.
Improved supervisor observability: it now reports metrics for its outbound requests, making failed calls to upstream services easier to monitor.
The runs list on a task's page now updates live — run statuses change and newly triggered runs appear without a manual refresh, matching the main Runs page.
Speed up the Batches list page for environments with a large number of batches, which could previously time out while loading.
Container startup no longer prints database and ClickHouse connection strings (with credentials) to the logs.
The tasks page no longer runs two queries whose results were never displayed, cutting wasted work on every page load and removing a source of hidden server errors
All packages: v4.5.8
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.5.7
23 Jul 2026- Deprecated
Add
node-24andnode-26as supportedruntimeoptions intrigger.config.ts. Theexperimental-node-24andexperimental-node-26names are now deprecated aliases and emit a deprecation warning; switch tonode-24/node-26instead.import { defineConfig } from "@trigger.dev/sdk"; export default defineConfig({ runtime: "node-24", project: "<your-project-ref>", }); Avoid logging task run environment variable values at debug level
Custom chat agent loops get two ergonomic wins for owning the turn loop.
chat.writeTurnComplete()now returns the turn boundary's resume cursors (lastEventIdfor the output stream andsessionInEventIdfor the input stream), so you can persist them straight from the task instead of round-tripping them back from the client.const { lastEventId, sessionInEventId } = await chat.writeTurnComplete(); await db.chats.update(chatId, { lastEventId, sessionInEventId });chat.pipeAndCapture()no longer throws when a stream is stopped or fails. It now returns aPipeAndCaptureResultwhosemessageholds any partial output captured before the stop or failure, alongside a typedstatus("complete" | "aborted" | "error") and, on failure, theerror. Read the message off the result:const { message, status, error } = await chat.pipeAndCapture(result, { signal, }); if (message) conversation.addResponse(message); if (status === "error") logger.error("turn failed", { error });Note:
pipeAndCapturepreviously resolved toUIMessage | undefined. Update call sites to read.messagefrom the returned result.
trigger.dev v4.5.7
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.5.7Release notes
Read the full release notes: trigger.dev/changelog/v4-5-7
Improvements
- Deprecated
Add
node-24andnode-26as supportedruntimeoptions intrigger.config.ts. Theexperimental-node-24andexperimental-node-26names are now deprecated aliases and emit a deprecation warning; switch tonode-24/node-26instead.import { defineConfig } from "@trigger.dev/sdk"; export default defineConfig({ runtime: "node-24", project: "<your-project-ref>", }); Avoid logging task run environment variable values at debug level
Custom chat agent loops get two ergonomic wins for owning the turn loop.
chat.writeTurnComplete()now returns the turn boundary's resume cursors (lastEventIdfor the output stream andsessionInEventIdfor the input stream), so you can persist them straight from the task instead of round-tripping them back from the client.const { lastEventId, sessionInEventId } = await chat.writeTurnComplete(); await db.chats.update(chatId, { lastEventId, sessionInEventId });chat.pipeAndCapture()no longer throws when a stream is stopped or fails. It now returns aPipeAndCaptureResultwhosemessageholds any partial output captured before the stop or failure, alongside a typedstatus("complete" | "aborted" | "error") and, on failure, theerror. Read the message off the result:const { message, status, error } = await chat.pipeAndCapture(result, { signal, }); if (message) conversation.addResponse(message); if (status === "error") logger.error("turn failed", { error });Note:
pipeAndCapturepreviously resolved toUIMessage | undefined. Update call sites to read.messagefrom the returned result.Suppress a build-time warning that could appear in Vite-based projects when the optional
@ai-sdk/otelpackage is not installed.
Bug fixes
Fixes intermittent
trigger devrun crashes where a run could fail at boot with a crypticCannot find module .../dev-run-worker.mjsafter a rebuild had cleaned up the build directory the run was launched against. Dev runs now retry cleanly instead of hard-crashing when their build directory is missing, the dev watchdog no longer removes the build tree of a still-running session, and a run assigned to a worker version that was superseded by a rebuild now fails fast with a clear message instead of silently hanging until it times out.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Refreshed the side menu: separate organization and account menus, a new project switcher, and the menu is now resizable by dragging its edge. The account Profile page has also been redesigned.
Allow different organization members to use the same development branch name without sharing or colliding with each other's branch environments.
Limit account settings email input to 254 characters.
Prevent duplicate Staging and Preview environments when account setup requests overlap
Fix the docs link on the empty Prompts page, which pointed to a page that no longer exists.
All packages: v4.5.7
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.5.6
21 Jul 2026- Breaking
Self-hosted deployments no longer ship shared default credentials; fresh installs generate their own. If yours still uses a previously published default, set a unique value before upgrading, or set
ALLOW_INSECURE_DEFAULT_SECRETS=trueto keep booting while you migrate. - Security
Require explicit browser approval for CLI and MCP login, with resilient polling while approval is pending.
- Security
Deployed task telemetry now reports the deployment identifier (e.g.
deployment_abc123) in theworker.idattribute, instead of an opaque internal value. Upgrade to get the readable identifier in your own OpenTelemetry exporters.
trigger.dev v4.5.6
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.5.6Release notes
Read the full release notes: trigger.dev/changelog/v4-5-6
Breaking changes
- Breaking
Self-hosted deployments no longer ship shared default credentials; fresh installs generate their own. If yours still uses a previously published default, set a unique value before upgrading, or set
ALLOW_INSECURE_DEFAULT_SECRETS=trueto keep booting while you migrate.
Security patches
- Security
Require explicit browser approval for CLI and MCP login, with resilient polling while approval is pending.
- Security
Deployed task telemetry now reports the deployment identifier (e.g.
deployment_abc123) in theworker.idattribute, instead of an opaque internal value. Upgrade to get the readable identifier in your own OpenTelemetry exporters. - Security
Prevent prototype pollution when applying run metadata operations or reconstructing nested telemetry attributes, while preserving legitimate
constructorandprototypefields. - Security
Add helpers to mint and verify the deployment-scoped token used to authenticate run controllers to the platform.
- Security
Added optional request rate limiting for telemetry ingestion endpoints.
- Security
Background-worker deployment lookups are now scoped to the authenticated environment.
- Security
Updating a GitHub App installation from the callback flow is now scoped to your own organization, so an installation ID belonging to another organization can no longer be used to refresh that organization's installation record. The GitHub App installation session is also now single-use, so completing an installation callback invalidates its state and it can no longer be replayed.
- Security
Scope schedule and environment-variable writes to the caller's project and environment
- Security
Reject compute snapshot callbacks that do not match the snapshot request that created them.
- Security
Require secret-key authentication to initialize the session out (agent→client) stream, matching the append route.
- Security
Live run and trace subscriptions now validate their identifiers more strictly and only return data from your own organization.
- Security
Window-function names in the query compiler are now validated against the allowlist, matching how other function calls are handled.
- Security
Authenticate run controllers to the platform with a signed, deployment-scoped token.
- Security
Verify that worker actions (starting, completing, and continuing a run, and reading its snapshots) target a run belonging to the caller's environment.
All packages: v4.5.6
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.5.5
20 Jul 2026- Removed
Remove the deprecated realtime stream write endpoint used by retired v3 task clients.
Add experimental Node.js 24 and 26 task runtimes. Set
runtimetoexperimental-node-24orexperimental-node-26intrigger.config.ts.Add
defaultRegionto the project GET and list API responses; null when unset.
trigger.dev v4.5.5
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.5.5Release notes
Read the full release notes: trigger.dev/changelog/v4-5-5
Improvements
Add experimental Node.js 24 and 26 task runtimes. Set
runtimetoexperimental-node-24orexperimental-node-26intrigger.config.ts.Add
defaultRegionto the project GET and list API responses; null when unset.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Transient internal sync failures are now retried quietly instead of surfacing as errors.
Optionally route ClickHouse read traffic to a read replica while writes stay on the primary. Set
CLICKHOUSE_READER_URLto move all reads, or target the busiest paths withRUNS_LIST_CLICKHOUSE_URL(runs list) andEVENTS_READER_CLICKHOUSE_URL(traces, spans, logs). All optional; unset keeps current behavior.- Removed
Remove the deprecated realtime stream write endpoint used by retired v3 task clients.
Fix batchTrigger requests that set a per-item idempotency key failing with an error instead of creating and deduplicating the runs
Speed up idempotency checks on
batchTriggercalls that use idempotency keys. Large batches against a task with a big run history no longer degrade to multi-second lookups.The "Preview branches" usage on the Limits page now counts only preview branches.
Avoid opening a redundant database connection pool when the legacy and primary databases are the same server, preventing connection usage from doubling.
Fix pages occasionally loading unstyled or failing to load during a deploy. The dashboard now reloads automatically to recover.
All packages: v4.5.5
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.5.4
14 Jul 2026- Breaking
Trigger.dev v3 is no longer supported. For self-hosted deployments, 4.5.0 is the last version we officially support for running v3; stay on 4.5.0 or upgrade to v4. v3 triggers, batch triggers, reschedules, and deploys now return a clear upgrade message instead of running.
- Removed
Remove the legacy
--mcpand--mcp-portoptions from thedevcommand. Run the dedicatedtrigger mcpcommand to start the Trigger.dev MCP server. You can now mark environment variables synced via the
syncEnvVarsbuild extension as secrets. Return{ name, value, isSecret: true }from your callback and those variables are stored redacted in the dashboard, just like manually created secret env vars.
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.5.4Release notes
Read the full release notes: trigger.dev/changelog/v4-5-4
Breaking changes
- Breaking
Trigger.dev v3 is no longer supported. For self-hosted deployments, 4.5.0 is the last version we officially support for running v3; stay on 4.5.0 or upgrade to v4. v3 triggers, batch triggers, reschedules, and deploys now return a clear upgrade message instead of running.
Improvements
You can now mark environment variables synced via the
syncEnvVarsbuild extension as secrets. Return{ name, value, isSecret: true }from your callback and those variables are stored redacted in the dashboard, just like manually created secret env vars.- Removed
Remove the legacy
--mcpand--mcp-portoptions from thedevcommand. Run the dedicatedtrigger mcpcommand to start the Trigger.dev MCP server. Removed the unused
ResourceMonitorexport from@trigger.dev/core/v3/serverOnly. It was a server-side logging helper with no remaining consumers.Removed the unused
@trigger.dev/core/v3/zodNamespaceexport and the legacy v3 socket message schemas. These were only used by the now-retired v3 engine and have no v4 consumers.
Bug fixes
Fix a
chat.agentmessage-loss race where sending a message right after an action (such as an undo) could drop the follow-up's response from the UI until a refresh.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Added
EVENT_REPOSITORY_POSTGRES_WRITES_DISABLEDto skip all PostgreSQL task-event writes for deployments that store task events in ClickHouse. Leave it off unlessEVENT_REPOSITORY_DEFAULT_STOREisclickhouse_v2, otherwise task events are lost.Promo credits: a /promo signup landing page, redeeming a promo code when a new org selects a plan, and showing remaining credits on the usage page.
Speed up retrieving a background worker by version. The endpoint no longer runs a slow lookup that scanned the full task table for large deployments; it now reuses data it already loads, so the response is the same but returns much faster.
Clearer login error when an email address is blocked by the WHITELISTED_EMAILS setting: the message now explains the address isn't allowed on this instance instead of the ambiguous "This email is unauthorized".
Make the native build server the default in project build settings. It's now opt-out, stored as a new
disableNativeBuildServerkey. Also clarifies in the UI that build settings apply to GitHub-triggered and native build server deployments.Optionally process high-volume telemetry ingestion in parallel for higher throughput under heavy load by setting
OTEL_TRANSFORM_WORKER_POOL_ENABLED=1. Off by default.Add a
REALTIME_BACKEND_DEFAULTenv var to choose the default realtime backend (electric,native, orshadow) for environments whose org has no per-org override. Defaults toelectric, so existing behavior is unchanged.Clarified on the Regions page that a region only affects where your runs execute, not where your data is stored. This shows as a tooltip on the Location column and in the confirmation dialog when you change your default region.
Improved the reliability of how run data is read and written.
Fixed stale login errors: an error from a previous login attempt (for example a rejected email address) no longer keeps reappearing on the login page and no longer makes later, successful attempts look like they failed.
The Errors page now shows better details for each error. Errors that don't carry a message — such as errors thrown without a message, or values thrown that aren't
Errorobjects — get a meaningful title instead of all reading "Unknown error", and are grouped by their name (or value) rather than collapsed into a single group. The error type now shows the actual error name, and stack traces now appear where previously they were missing.Return a clear client error when SSO form submissions use an unsupported content type
Query page: extracting fields from a run's output with JSON functions (such as JSONExtractString or JSONExtractInt) no longer fails with an "illegal type: JSON" error.
All packages: v4.5.4
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.5.3
10 Jul 2026- Breaking
Removed support for the end-of-life v3
trigger devCLI. Starting a dev session with an old v3 CLI now returns an upgrade message instead of connecting - upgrade to the v4 CLI to continue usingtrigger dev. Fix TS2742 ("inferred type cannot be named") when exporting a
chat.agentfrom a project with declaration emit:ChatTaskWirePayloadandChatInputChunkare now declared in the public@trigger.dev/sdk/chatsubpath, so inferred agent types emit portable declarations and the wire types are directly importable.Reduce primary database load on the runs page by serving its empty-state check from ClickHouse instead of Postgres.
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.5.3Release notes
Read the full release notes: trigger.dev/changelog/v4-5-3
Breaking changes
- Breaking
Removed support for the end-of-life v3
trigger devCLI. Starting a dev session with an old v3 CLI now returns an upgrade message instead of connecting - upgrade to the v4 CLI to continue usingtrigger dev.
Bug fixes
Fix TS2742 ("inferred type cannot be named") when exporting a
chat.agentfrom a project with declaration emit:ChatTaskWirePayloadandChatInputChunkare now declared in the public@trigger.dev/sdk/chatsubpath, so inferred agent types emit portable declarations and the wire types are directly importable.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Reduce primary database load on the runs page by serving its empty-state check from ClickHouse instead of Postgres.
Fixed submitting your email on the login page reloading back to an empty form instead of showing the magic link confirmation screen.
All packages: v4.5.3
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.5.2
9 Jul 2026- Security
Harden account and access-control handling across auth, RBAC, org membership, and impersonation.
- Security
Harden URL handling for alert webhooks and platform notifications.
- Security
Harden the query and prompt-override APIs and rate-limit the query ai-title endpoint.
trigger.dev v4.5.2
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.5.2Release notes
Read the full release notes: trigger.dev/changelog/v4-5-2
Security
- Security
Harden account and access-control handling across auth, RBAC, org membership, and impersonation.
- Security
Harden URL handling for alert webhooks and platform notifications.
- Security
Harden the query and prompt-override APIs and rate-limit the query ai-title endpoint.
- Security
Improve redaction of secrets from debug logs.
- Security
Tighten environment scoping when replaying a run.
- Security
Scope run, batch, and trigger lookups to the caller's tenant.
- Security
Honor the MCP server's
--dev-onlyflag.
Features
Bulk actions allow runs to be re-run based on a filter or run IDs. Now it's also available via API and in the official SDK. Create, list, retrieve, poll and abort bulk actions. Runs can be targeted to a different compute region, just like in the web UI.
Improvements
Large batch payloads now offload to object storage instead of riding inline in the trigger request.
batchTriggerandbatchTriggerAndWait(and the by-id and by-task variants) offload any per-item payload over 128KB before sending, the same way singletriggerandtriggerAndWaitalready do, so a big batch no longer blows past the API body limit.Removed internal helpers that were only used by the end-of-life v3 self-hosted compute providers.
Add an
onEventcallback toTriggerChatTransport/useTriggerChatTransportthat emits typed lifecycle events for sends, stream connects, first chunk, and turn completion. Send-success metrics, time-to-first-token, and "sent but never answered" watchdogs become a few lines of client code.onEvent: (event) => { if (event.type === "message-sent") metrics.timing("chat.send_ms", event.durationMs); if (event.type === "first-chunk") metrics.timing("chat.ttft_ms", event.sinceSendMs ?? 0); },The environment and branch selector dropdown will automatically revalidate when opened so that new branches show up.
A cleaner sign-in flow: request a magic link right from the login page, or continue with SSO.
Serve PostHog analytics from a same-origin
/phpath that reverse-proxies to PostHog Cloud EU, following PostHog's first-party reverse-proxy guidance.Refreshed the SSO & Directory Sync settings page layout and copy.
Migrated the webapp to Tailwind CSS v4 with a CSS-first
@theme. Semantic color tokens are now CSS variables overridable per theme. Tailwind runs through@tailwindcss/postcss; plugins replaced or upgraded to v4-compatible versions.Replaced raw charcoal-* Tailwind classes with semantic theme tokens across the dashboard. Adds surface, border, and text tokens to the themable layer so future themes only override CSS variables.
Bug fixes
Fix chat turns that throw, for example from an
onTurnStarthook, leaking their message listener, which lost or duplicated messages sent during later turns.Fix
chat.agentandchat.createSessionpermanently dropping user messages when several arrived during a single turn: every buffered message is now dispatched as its own turn instead of only the first.Fix chat continuation runs replaying already-answered messages: turns delivered while the run was suspended now advance the session.in resume cursor, so a new run picks up exactly where the previous one left off.
Fix
chat.createSessionswallowing a message sent shortly after stopping a turn: the turn's message listener now detaches when the stream settles, so those messages run as the next turn.Anchor batch item run-ops residency on the batch's own friendlyId so a mid-batch flag change can no longer mint an item into a different physical store than its
BatchTaskRunrow.AI generation cost now uses the exact provider-reported cost from OpenRouter/Vercel AI Gateway when present, instead of catalog pricing, so cache-discounted and fallback-routed requests match the amount the provider actually billed.
Deleting a project no longer triggers a slow database cleanup that could hang on projects with many runs.
Fixed the agent playground chat failing to send messages, with "Failed to fetch" errors in some environments. Messages now reach the agent reliably.
Deploying with an outdated CLI could produce an image that fails to start on every run. These deploys are now stopped before going live, with a message asking you to upgrade the CLI and re-deploy.
Runs resuming after a wait no longer fail with
TASK_EXECUTION_ABORTEDwhen the database is briefly unreachable; the resume endpoint returns a retryable response for transient infrastructure errors instead of a permanent one.
All packages: v4.5.2
@trigger.dev/build, @trigger.dev/core, @trigger.dev/plugins, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.5.1
6 Jul 2026Extend the SSO plugin contract with WorkOS Directory Sync (SCIM) support.
trigger.dev v4.5.1
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.5.1Release notes
Read the full release notes: trigger.dev/changelog/v4-5-1
Improvements
Extend the SSO plugin contract with WorkOS Directory Sync (SCIM) support.
All packages: v4.5.1
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.5.0
2 Jul 2026AI SDK 7 support (v5 and v6 still supported), with OpenTelemetry telemetry auto-wired
Large trigger-payload offload: trigger payloads at or above 128KB upload to object storage automatically, using the same auth and baseURL as the trigger call
Region support on the runs API: filter runs by region and read each run's executing region (also on MCP
list_runs)
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.5.0Release notes
Read the full release notes: trigger.dev/changelog/v4-5-0
AI Agents (
chat.agent)Run Vercel AI SDK chat completions as durable Trigger.dev tasks instead of fragile API routes. A conversation runs as one long-lived task keyed on
chatId, so it survives page refreshes, network blips, redeploys, and crashes, and every turn is a span in the dashboard.import { chat } from "@trigger.dev/sdk/ai"; import { streamText, stepCountIs } from "ai"; import { anthropic } from "@ai-sdk/anthropic"; export const myChat = chat.agent({ id: "my-chat", run: async ({ messages, signal }) => { return streamText({ ...chat.toStreamTextOptions(), // system prompt, compaction, steering, telemetry model: anthropic("claude-sonnet-4-5"), messages, abortSignal: signal, stopWhen: stepCountIs(15), }); }, });Sessions
The durable primitive underneath
chat.agent, usable on its own: a run-aware, bidirectional stream channel keyed on a stableexternalIdwhose.in/.outstreams survive run boundaries (suspend, crash, idle-timeout, redeploy). One Session spans many runs, which makes it a good fit for agent inboxes and approval flows.import { sessions } from "@trigger.dev/sdk"; // Create the session and trigger its first run (idempotent on externalId) await sessions.start({ type: "inbox", externalId: userId, taskIdentifier: "inbox-agent", }); const session = sessions.open(userId); await session.in.send({ text: "hello" }); const stream = await session.out.read({ signal: AbortSignal.timeout(30_000) }); for await (const chunk of stream) console.log(chunk); // durable across run swapsAI Prompts
Define prompt templates as code, versioned on every deploy, and override the text or model from the dashboard without redeploying (environment-scoped). Each generation links back to its prompt version for usage, cost, and latency.
import { prompts } from "@trigger.dev/sdk"; import { z } from "zod"; export const supportPrompt = prompts.define({ id: "customer-support", model: "gpt-4o", variables: z.object({ customerName: z.string(), issue: z.string() }), content: `You are a support agent for Acme. Customer: {{customerName}} Issue: {{issue}}`, }); // Honors any active dashboard override, else the current deployed version const resolved = await supportPrompt.resolve({ customerName: "Alice", issue: "Can't log in" }); // resolved.text, resolved.model, resolved.versionuseChatintegrationuseTriggerChatTransportis a Vercel AI SDKChatTransportthat runsuseChatover Trigger.dev realtime with no API routes. Text, tool calls, reasoning, anddata-*parts stream natively, and it works with AI SDK v5, v6, and now v7.First-turn fast path (
chat.headStart)Runs the first turn in your warm server process while the agent boots in parallel, cutting cold-start time-to-first-chunk roughly in half (measured ~2.8s to ~1.2s). Available via the new
@trigger.dev/sdk/chat-serversubpath.Human-in-the-loop, stop, and steering
The agent control surface: tool approvals (
needsApproval+addToolApprovalResponse), client-driven stop-generation, mid-execution steering (pendingMessages), and between-turn context injection (chat.inject/chat.defer), all durable across the conversation.Agent Skills
skills.define({ id, path })bundles aSKILL.mdfolder into your deploy image. The agent gets a one-line summary up front and loads the full instructions plus scopedbash/readFiletools on demand (progressive disclosure), so a capability is something the model reaches for rather than a pre-declared typed tool.trigger skillsfor coding assistantstrigger skillsinstalls version-pinned Trigger.dev skills plus a bundled docs snapshot into Claude Code, Cursor, GitHub Copilot, and Codex, so your assistant's Trigger.dev knowledge stays current with your installed SDK version.trigger initnow offers to set up the MCP server and skills too.Model library
A new Models page in the dashboard: a catalog of models grouped by provider with context window, capabilities, and input / output pricing per 1M tokens, plus a "Your models" tab showing per-model usage, cost, and cache-hit sparklines from your actual traffic.
Dev branches
Run multiple local
trigger devsessions in parallel (separate git worktrees or coding agents) without runs colliding, each isolated with its own dashboard, viatrigger dev --branch <name>.TriggerClientAn instantiable client so one process can trigger and read across projects, environments, and preview branches, each with its own auth and baseURL, with no shared global state.
import { TriggerClient } from "@trigger.dev/sdk"; const prod = new TriggerClient({ accessToken: process.env.TRIGGER_PROD_KEY }); const preview = new TriggerClient({ accessToken: process.env.TRIGGER_PREVIEW_KEY, previewBranch: "signup-flow", }); await prod.tasks.trigger("send-email", { to: "user@example.com" }); await preview.runs.list({ status: ["COMPLETED"] });SDK and runtime
AI SDK 7 support (v5 and v6 still supported), with OpenTelemetry telemetry auto-wired
Large trigger-payload offload: trigger payloads at or above 128KB upload to object storage automatically, using the same auth and baseURL as the trigger call
Region support on the runs API: filter runs by region and read each run's executing region (also on MCP
list_runs)Duplicate task-id detection:
devanddeployfail with a clear error instead of silently overwritingenvvars.uploadgains anisSecretflag to import redacted secret variablesRetry hardening:
TASK_MIDDLEWARE_ERRORnow retries under the task's retry policy
All packages: v4.5.0
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.4.6
12 May 2026Fail attempts on uncaught exceptions instead of hanging to
MAX_DURATION_EXCEEDED. A NodeEventEmitter(e.g.node-redis) emitting"error"with no.on("error", ...)listener escalates touncaughtException, which the worker previously reported but did not act on — runs drifted to maxDuration with empty attempts. They now fail fast with the original error and statusFAILED, and respect the task's normal retry policy. You should still attach.on("error", ...)listeners to long-lived clients to handle errors gracefully.Fix dev workers spinning at 100% CPU after the parent CLI disconnects. Orphaned
trigger-dev-run-worker(and indexer) processes were caught in anuncaughtExceptionfeedback loop: a periodic IPC send viaprocess.sendwould throwERR_IPC_CHANNEL_CLOSEDonce the parent closed the channel, which re-entered the same handler that itself calledprocess.send, scheduled viasetImmediateand amplified by source-map-support'sprepareStackTrace. Fixed by (1) silently dropping packets inZodIpcConnectionwhen the channel is disconnected, (2) adding aprocess.on("disconnect", ...)handler in dev workers so they exit cleanly when the CLI closes the IPC channel, and (3) wrapping alluncaughtException-pathprocess.sendcalls in asafeSendguard that checksprocess.connectedand swallows synchronous throws.
trigger.dev v4.4.6
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.4.6Release notes
Read the full release notes: trigger.dev/changelog/v4-4-6
Improvements
Fail attempts on uncaught exceptions instead of hanging to
MAX_DURATION_EXCEEDED. A NodeEventEmitter(e.g.node-redis) emitting"error"with no.on("error", ...)listener escalates touncaughtException, which the worker previously reported but did not act on — runs drifted to maxDuration with empty attempts. They now fail fast with the original error and statusFAILED, and respect the task's normal retry policy. You should still attach.on("error", ...)listeners to long-lived clients to handle errors gracefully.
Bug fixes
Fix dev workers spinning at 100% CPU after the parent CLI disconnects. Orphaned
trigger-dev-run-worker(and indexer) processes were caught in anuncaughtExceptionfeedback loop: a periodic IPC send viaprocess.sendwould throwERR_IPC_CHANNEL_CLOSEDonce the parent closed the channel, which re-entered the same handler that itself calledprocess.send, scheduled viasetImmediateand amplified by source-map-support'sprepareStackTrace. Fixed by (1) silently dropping packets inZodIpcConnectionwhen the channel is disconnected, (2) adding aprocess.on("disconnect", ...)handler in dev workers so they exit cleanly when the CLI closes the IPC channel, and (3) wrapping alluncaughtException-pathprocess.sendcalls in asafeSendguard that checksprocess.connectedand swallows synchronous throws.
All packages: v4.4.6
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.4.5
1 May 2026- Breaking
Add server-side deprecation gate for deploys from v3 CLI versions (gated by
DEPRECATE_V3_CLI_DEPLOYS_ENABLED). v4 CLI deploys are unaffected. - Security
Upgrade Remix packages from 2.1.0 to 2.17.4 to address security vulnerabilities in React Router
Add
--no-browserflag toinitandloginto skip auto-opening the browser during authentication. Also error loudly wheninitis run without--yesunder non-TTY stdin (previously default-and-exited silently, leaving the project half-initialized). Both commands now show anExamplessection in--help.
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.4.5Release notes
Read the full release notes: trigger.dev/changelog/v4-4-5
Breaking changes
- Breaking
Add server-side deprecation gate for deploys from v3 CLI versions (gated by
DEPRECATE_V3_CLI_DEPLOYS_ENABLED). v4 CLI deploys are unaffected.
Improvements
Add
--no-browserflag toinitandloginto skip auto-opening the browser during authentication. Also error loudly wheninitis run without--yesunder non-TTY stdin (previously default-and-exited silently, leaving the project half-initialized). Both commands now show anExamplessection in--help.Add
isReplayboolean to the run context (ctx.run.isReplay), derived from the existingreplayedFromTaskRunFriendlyIddatabase field. Defaults tofalsefor backwards compatibility.Redact the
resolveWaitpointruntime log so it only emitsidandtypeinstead of the full completed waitpoint. Previously the log printed the entire waitpoint (includingoutput) to stdout in production runs, which could leak sensitive payloads. The value returned bywait.forToken()is unchanged.Add
SessionIdfriendly ID generator and schemas for the new durable Session primitive. Exported from@trigger.dev/core/v3/isomorphicalongsideRunId,BatchId, etc. Ships theCreateSessionStreamWaitpointrequest/response schemas alongside the main Session CRUD.Truncate large error stacks and messages to prevent OOM crashes. Stack traces are capped at 50 frames (keeping top 5 + bottom 45 with an omission notice), individual stack lines at 1024 chars, and error messages at 1000 chars. Applied in parseError, sanitizeError, and OTel span recording.
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Add a "Back office" tab to
/adminand a per-organization detail page at/admin/back-office/orgs/:orgId. The first action available on that page is editing the org's API rate limit: admins can save atokenBucketoverride (refill rate, interval, max tokens) and see a plain-English preview of the resulting sustained rate and burst allowance. Writes are audit-logged via the server logger.Optional
DEPLOY_REGISTRY_ECR_DEFAULT_REPOSITORY_POLICYenv var to apply a default repository policy when the webapp creates new ECR reposShip the Errors page to all users, with a polish + bug-fix pass: pinned "No channel" item in the Slack alert channel picker, viewer-timezone alert timestamps via Slack's
<!date^>token, Activity sparkline peak tooltip, centered loading spinner and bug-icon empty state on the error detail page, ellipsis on the Configure alerts trigger.Configure the set of machine presets to build boot snapshots for at deploy time via
COMPUTE_TEMPLATE_MACHINE_PRESETS(CSV of preset names, defaultsmall-1x). UseCOMPUTE_TEMPLATE_MACHINE_PRESETS_REQUIRED(CSV, default = full PRESETS list) to scope which preset failures fail a required-mode deploy. Optional preset failures are logged and don't block the deploy.Regenerating a RuntimeEnvironment API key no longer invalidates the previous key immediately. The old key is recorded in a new
RevokedApiKeytable with a 24 hour grace window, andfindEnvironmentByApiKeyfalls back to it when the submitted key doesn't match any live environment. The grace window can be ended early (or extended) by updatingexpiresAton the row.Add the
Sessionprimitive — a durable, task-bound, bidirectional I/O channel that outlives a single run and acts as the run manager forchat.agent. Ships the PostgresSession+SessionRuntables, ClickHousesessions_v1+ replication service, thesessionsJWT scope, and the public CRUD + realtime routes (/api/v1/sessions,/realtime/v1/sessions/:session/:io) includingend-and-continuefor server-orchestrated run handoffs and session-stream waitpoints.Add
KUBERNETES_POD_DNS_NDOTS_OVERRIDE_ENABLEDflag (off by default) that overrides the cluster default and setsdnsConfig.options.ndotson runner pods (defaulting to 2, configurable viaKUBERNETES_POD_DNS_NDOTS). Kubernetes defaults pods tondots: 5, so any name with fewer than 5 dots — including typical external domains likeapi.example.com— is first walked through every entry in the cluster search list (<ns>.svc.cluster.local,svc.cluster.local,cluster.local) before being tried as-is, turning one resolution into 4+ CoreDNS queries (×2 with A+AAAA). Using a lowerndotsvalue reduces DNS query amplification in thecluster.localzone.Note: before enabling, make sure no code path relies on search-list expansion for names with dots ≥ the configured value — those names will hit their as-is form first and could resolve externally before falling back to the cluster search path.
Vercel integration option to disable auto promotions
Make it clear in the admin that feature flags are global and should rarely be changed.
Admin worker groups API: add GET loader and expose more fields on POST.
Add 60s fresh / 60s stale SWR cache to
getEntitlementinplatform.v3.server.ts. Eliminates a synchronous billing-service HTTP round trip on every trigger. Reuses the existingplatformCache(LRU memory + Redis) pattern already used forlimitsandusage. Cache key is${orgId}. Errors return a permissive{ hasAccess: true }fallback (existing behavior) and are also cached to prevent thundering-herd on billing outages.Show a
MicroVMbadge next to the region name on the regions page.Increase default maximum project count per organization from 10 to 25
Merge execution snapshot creation into the dequeue taskRun.update transaction, reducing 2 DB commits to 1 per dequeue operation
Add per-worker Node.js heap metrics to the OTel meter —
nodejs.memory.heap.used,nodejs.memory.heap.total,nodejs.memory.heap.limit,nodejs.memory.external,nodejs.memory.array_buffers,nodejs.memory.rss. Host-metrics only publishes RSS, which overstates V8 heap by the external + native footprint; these give direct heap visibility per cluster worker soNODE_MAX_OLD_SPACE_SIZEcan be sized against observed heap peaks rather than RSS.Tag Prisma spans with
db.datasource: "writer" | "replica"so monitors and trace queries can distinguish the writer pool from the replica pool. Applies to allprisma:engine:*spans (includingprisma:engine:connectionused by the connection-pool monitors) and the outerprisma:client:operationspan.Clarify the cross-region intent in the Terraform and AI-prompt helpers on the Add Private Connection page. Both already default
supported_regionsto["us-east-1", "eu-central-1"]; added an inline comment / parenthetical so the user understands why both regions are listed (Trigger.dev runs in both, so the service must be consumable from either).Add
RUN_ENGINE_READ_REPLICA_SNAPSHOTS_SINCE_ENABLEDflag (default off) to route the Prisma reads insideRunEngine.getSnapshotsSincethrough the read-only replica client. Offloads the snapshot polling queries (fired by every running task runner) from the primary. When disabled, behavior is unchanged.Stop creating TaskRunTag records and _TaskRunToTaskRunTag join table entries during task triggering. The denormalized runTags string array on TaskRun already stores tag names, making the M2M relation redundant write overhead.
Stop writing per-tick state (
lastScheduledTimestamp,nextScheduledTimestamp,lastRunTriggeredAt) onTaskScheduleandTaskScheduleInstance. The schedule engine now carries the previous fire time forward via the worker queue payload, eliminating ~270K dead-tuple-driven autovacuums per year on these hot tables and the associatedIO:XactSyncmini-spikes on the writer. Customer-facingpayload.lastTimestampsemantics are unchanged.Replace the expensive DISTINCT query for task filter dropdowns with a dedicated TaskIdentifier registry table backed by Redis. Environments migrate automatically on their next deploy, with a transparent fallback to the legacy query for unmigrated environments. Also fixes duplicate dropdown entries when a task changes trigger source, and adds active/archived grouping for removed tasks. Moves BackgroundWorkerTask reads in the trigger hot path to the read replica.
Public Access Tokens (PATs) minted before an API key rotation now keep working during the 24h grace window.
validatePublicJwtKeyfalls back to any non-expiredRevokedApiKeyrows for the signing environment when the primary signature check against the env's currentapiKeyfails. The fallback query only runs on the failure path, so the hot success path is unchanged.Batch items that hit the environment queue size limit now fast-fail without
retries and without creating pre-failed TaskRuns.Show the cancel button in the runs list for runs in
DEQUEUEDstatus.DEQUEUEDwas missing fromNON_FINAL_RUN_STATUSESso the list hid the button even though the single run page allowed it.Reduce 5xx feedback loops on hot debounce keys by quantizing
delayUntil,
adding an unlocked fast-path skip, and gracefully handling redlock
contention inhandleDebounceso the SDK no longer retries into a herd.Fix RSS memory leak in the realtime proxy routes.
/realtime/v1/runs,/realtime/v1/runs/:id, and/realtime/v1/batches/:idcalledfetch()into Electric with no abort signal, so when a client disconnected mid long-poll, undici kept the upstream socket open and buffered response chunks that would never be consumed — retained only in RSS, invisible to V8 heap tooling. ThreadgetRequestAbortSignal()throughRealtimeClient.streamRun/streamRuns/streamBatchtolongPollingFetchand cancel the upstream body in the error path. Isolated reproducer showed ~44 KB retained per leaked request; signal propagation releases it cleanly.Fix memory leak where every aborted SSE connection pinned the full request/response graph on Node 20, caused by
AbortSignal.any()insse.tsretaining its source signals indefinitely (see nodejs/node#54614, nodejs/node#55351). Also clear thesetTimeout(abort)timer inentry.server.tsxso successful HTML renders don't pin the React tree for 30s per request.Preserve filters on the queues page when submitting modal actions.
Fix Redis connection leak in realtime streams and broken abort signal propagation.
Redis connections: Non-blocking methods (ingestData, appendPart, getLastChunkIndex) now share a single Redis connection instead of creating one per request. streamResponse still uses dedicated connections (required for XREAD BLOCK) but now tears them down immediately via disconnect() instead of graceful quit(), with a 15s inactivity fallback.
Abort signal: request.signal is broken in Remix/Express due to a Node.js undici GC bug (nodejs/node#55428) that severs the signal chain when Remix clones the Request internally. Added getRequestAbortSignal() wired to Express res.on("close") via httpAsyncStorage, which fires reliably on client disconnect. All SSE/streaming routes updated to use it.
Prevent dashboard crash (React error #31) when span accessory item text is not a string. Filters out malformed accessory items in SpanCodePathAccessory instead of passing objects to React as children.
- Security
Upgrade Remix packages from 2.1.0 to 2.17.4 to address security vulnerabilities in React Router
Fix Vercel integration settings page (remove redundant section toggles) and improve the Vercel onboarding flow so the modal closes after connecting a GitHub repo and the marketplace
nextURL is preserved across the GitHub app install redirect.
All packages: v4.4.5
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.4.4
13 Apr 2026Add support for setting TTL (time-to-live) defaults at the task level and globally in trigger.config.ts, with per-trigger overrides still taking precedence
Large run outputs can use the new API which allows switching object storage providers.
Add platform notifications support to the CLI. The
trigger devandtrigger logincommands now fetch and display platform notifications (info, warn, error, success) from the server. Includes discovery-based filtering to conditionally show notifications based on project file patterns, color markup rendering for styled terminal output, and a non-blocking display flow with a spinner fallback for slow fetches. Use--skip-platform-notificationsflag withtrigger devto disable the notification check.
Upgrade
npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun
Self-hosted Docker image:
ghcr.io/triggerdotdev/trigger.dev:v4.4.4Release notes
Read the full release notes: trigger.dev/changelog/v4-4-4
Highlights
Add support for setting TTL (time-to-live) defaults at the task level and globally in trigger.config.ts, with per-trigger overrides still taking precedence
Large run outputs can use the new API which allows switching object storage providers.
CLI Improvements
Add platform notifications support to the CLI. The
trigger devandtrigger logincommands now fetch and display platform notifications (info, warn, error, success) from the server. Includes discovery-based filtering to conditionally show notifications based on project file patterns, color markup rendering for styled terminal output, and a non-blocking display flow with a spinner fallback for slow fetches. Use--skip-platform-notificationsflag withtrigger devto disable the notification check.
MCP Server improvements
Add
get_span_detailsMCP tool for inspecting individual spans within a run trace.Span IDs now shown in
get_run_detailstrace output for easy discoveryNew API endpoint
GET /api/v1/runs/:runId/spans/:spanIdget_query_schema— discover available TRQL tables and columnsquery— execute TRQL queries against your datalist_dashboards— list built-in dashboards and their widgetsrun_dashboard_query— execute a single dashboard widget querywhoami— show current profile, user, and API URLlist_profiles— list all configured CLI profilesswitch_profile— switch active profile for the MCP sessionstart_dev_server— starttrigger devin the background and stream outputstop_dev_server— stop the running dev serverdev_server_status— check dev server status and view recent logsGET /api/v1/query/schema— query table schema discoveryGET /api/v1/query/dashboards— list built-in dashboards--readonlyflag hides write tools (deploy,trigger_task,cancel_run) so the AI cannot make changesread:queryJWT scope for query endpoint authorizationget_run_detailstrace output is now paginated with cursor supportMCP tool annotations (
readOnlyHint,destructiveHint) for all toolsget_query_schemanow requires a table name and returns only one table's schema (was returning all tables)get_current_workerno longer inlines payload schemas; use newget_task_schematool insteadQuery results formatted as text tables instead of JSON (~50% fewer tokens)
cancel_run,list_deploys,list_preview_branchesformatted as text instead of raw JSONSchema and dashboard API responses cached to avoid redundant fetches
Adapted the CLI API client to propagate the trigger source via http headers.
--readonlyflag hides write tools (deploy,trigger_task,cancel_run) so the AI cannot make changesget_run_detailstrace output is now paginated with cursor supportMCP tool annotations (
readOnlyHint,destructiveHint) for all toolsget_query_schemanow requires a table name and returns only one table's schema (was returning all tables)get_current_workerno longer inlines payload schemas; use newget_task_schematool insteadQuery results formatted as text tables instead of JSON (~50% fewer tokens)
cancel_run,list_deploys,list_preview_branchesformatted as text instead of raw JSONSchema and dashboard API responses cached to avoid redundant fetches
Bug fixes
Fix dev CLI leaking build directories on rebuild, causing disk space accumulation. Deprecated workers are now pruned (capped at 2 retained) when no active runs reference them. The watchdog process also cleans up
.trigger/tmp/when the dev CLI is killed ungracefully (e.g. SIGKILL from pnpm).Fix
--loadflag being silently ignored on local/self-hosted builds.Fixed
search_docstool failing due to renamed upstream Mintlify tool (SearchTriggerDev→search_trigger_dev)Fixed
list_deploysfailing when deployments have nullruntime/runtimeVersionfieldsFixed
list_preview_branchescrashing due to incorrect response shape accessFixed
metricstable column documented asvalueinstead ofmetric_valuein query docsFixed dev CLI leaking build directories on rebuild — deprecated workers now clean up their build dirs when their last run completes
Fixed
search_docstool failing due to renamed upstream Mintlify tool (SearchTriggerDev→search_trigger_dev)Fixed
list_deploysfailing when deployments have nullruntime/runtimeVersionfieldsFixed
list_preview_branchescrashing due to incorrect response shape accessFixed
metricstable column documented asvalueinstead ofmetric_valuein query docsFixed dev CLI leaking build directories on rebuild — deprecated workers now clean up their build dirs when their last run completes
Server changes
These changes affect the self-hosted Docker image and Trigger.dev Cloud:
Add admin UI for viewing and editing feature flags (org-level overrides and global defaults).
Other improvements:
Add allowRollbacks query param to the promote deployment API to enable version downgrades
Add automatic LLM cost calculation for spans with GenAI semantic conventions. When a span arrives with
gen_ai.response.modeland token usage data, costs are calculated from an in-memory pricing registry backed by Postgres and dual-written to both span attributes (trigger.llm.*) and a newllm_metrics_v1ClickHouse table that captures usage, cost, performance (TTFC, tokens/sec), and behavioral (finish reason, operation type) metrics.Add API endpoint
GET /api/v1/runs/:runId/spans/:spanIdthat returns detailed span information including properties, events, AI enrichment (model, tokens, cost), and triggered child runs.Multi-provider object storage with protocol-based routing for zero-downtime migration
Add IAM role-based auth support for object stores (no access keys required).
Add platform notifications to inform users about new features, changelogs, and platform events directly in the dashboard.
Add private networking support via AWS PrivateLink. Includes BillingClient methods for managing private connections, org settings UI pages for connection management, and supervisor changes to apply
privatelinkpod labels for CiliumNetworkPolicy matching.Reduce run start latency by skipping the intermediate queue when concurrency is available. This optimization is rolled out per-region and enabled automatically for development environments.
Extended the search filter on the environment variables page to match on environment type (production, staging, development, preview) and branch name, not just variable name and value.
Set
application_nameon Prisma connections from SERVICE_NAME so DB load can be attributed by serviceFix transient R2/object store upload failures during batchTrigger() item streaming.
Added p-retry (3 attempts, 500ms–2s exponential backoff) around
uploadPacketToObjectStoreinBatchPayloadProcessor.process()so transient network errors self-heal server-side rather than aborting the entire batch stream.Removed
x-should-retry: falsefrom the 500 response on the batch items route so the SDK's existing 5xx retry path can recover if server-side retries are exhausted. Item deduplication by index makes full-stream retries safe.
Concurrency-keyed queues now use a single master queue entry per base queue instead of one entry per key. Prevents high-CK-count tenants from consuming the entire parentQueueLimit window and starving other tenants on the same shard.
Reduce lock contention when processing large
batchTriggerAndWaitbatches. Previously, each batch item acquired a Redis lock on the parent run to insert aTaskRunWaitpointrow, causingLockAcquisitionTimeoutErrorwith high concurrency (880 errors/24h in prod). SinceblockRunWithCreatedBatchalready transitions the parent toEXECUTING_WITH_WAITPOINTSbefore items are processed, the per-item lock is unnecessary. The newblockRunWithWaitpointLocklessmethod performs only the idempotent CTE insert without acquiring the lock.Strip
securequery parameter from QUERY_CLICKHOUSE_URL before passing to ClickHouse client. This was already done for the main and logs ClickHouse clients but was missing for the query client, causing a startup crash withError: Unknown URL parameters: secure.Fix
OrganizationsPresenter.#getEnvironmentmatching the wrong development environment on teams with multiple members. All dev environments share the slug"dev", so the previousfindby slug alone could return another member's environment. Now filters DEVELOPMENT environments byorgMember.userIdto ensure the logged-in user's dev environment is selected.
All packages: v4.4.4
@trigger.dev/build, @trigger.dev/core, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, trigger.dev
4.4.3
10 Mar 2026Reading the note…
4.4.2
4 Mar 2026Reading the note…
4.4.1
20 Feb 2026Reading the note…
4.4.0
19 Feb 2026Added
query.execute()which lets you query your Trigger.dev data using TRQL (Trigger Query Language) and returns results as typed JSON rows or CSV. It supports configurable scope (environment, project, or organization), time filtering viaperiodorfrom/toranges, and aformatoption for JSON or CSV output.import { query } from "@trigger.dev/sdk"; import type { QueryTable } from "@trigger.dev/sdk"; // Basic untyped query const result = await query.execute("SELECT run_id, status FROM runs LIMIT 10"); // Type-safe query using QueryTable to pick specific columns const typedResult = await query.execute<QueryTable<"runs", "run_id" | "status" | "triggered_at">>( "SELECT run_id, status, triggered_at FROM runs LIMIT 10" ); typedResult.results.forEach((row) => { console.log(row.run_id, row.status); // Fully typed }); // Aggregation query with inline types const stats = await query.execute<{ status: string; count: number }>( "SELECT status, COUNT(*) as count FROM runs GROUP BY status", { scope: "project", period: "30d" } ); // CSV export const csv = await query.execute("SELECT run_id, status FROM runs", { format: "csv", period: "7d", }); console.log(csv.results); // Raw CSV stringAdd
maxDelayoption to debounce feature. This allows setting a maximum time limit for how long a debounced run can be delayed, ensuring execution happens within a specified window even with continuous triggers.await myTask.trigger(payload, { debounce: { key: "my-key", delay: "5s", maxDelay: "30m", // Execute within 30 minutes regardless of continuous triggers }, });Aligned the SDK's
getRunIdForOptionslogic with the Core package to handle semantic targets (root,parent) in root tasks.
Minor Changes
Added
query.execute()which lets you query your Trigger.dev data using TRQL (Trigger Query Language) and returns results as typed JSON rows or CSV. It supports configurable scope (environment, project, or organization), time filtering viaperiodorfrom/toranges, and aformatoption for JSON or CSV output.import { query } from "@trigger.dev/sdk"; import type { QueryTable } from "@trigger.dev/sdk"; // Basic untyped query const result = await query.execute("SELECT run_id, status FROM runs LIMIT 10"); // Type-safe query using QueryTable to pick specific columns const typedResult = await query.execute<QueryTable<"runs", "run_id" | "status" | "triggered_at">>( "SELECT run_id, status, triggered_at FROM runs LIMIT 10" ); typedResult.results.forEach((row) => { console.log(row.run_id, row.status); // Fully typed }); // Aggregation query with inline types const stats = await query.execute<{ status: string; count: number }>( "SELECT status, COUNT(*) as count FROM runs GROUP BY status", { scope: "project", period: "30d" } ); // CSV export const csv = await query.execute("SELECT run_id, status FROM runs", { format: "csv", period: "7d", }); console.log(csv.results); // Raw CSV string
Patch Changes
Add
maxDelayoption to debounce feature. This allows setting a maximum time limit for how long a debounced run can be delayed, ensuring execution happens within a specified window even with continuous triggers.await myTask.trigger(payload, { debounce: { key: "my-key", delay: "5s", maxDelay: "30m", // Execute within 30 minutes regardless of continuous triggers }, });Aligned the SDK's
getRunIdForOptionslogic with the Core package to handle semantic targets (root,parent) in root tasks.Export
AnyOnStartAttemptHookFunctiontype to allow definingonStartAttempthooks for individual tasks.Fixed a minor issue in the deployment command on distinguishing between local builds for the cloud vs local builds for self-hosting setups.
4.3.3
23 Jan 2026Reading the note…
4.3.2
8 Jan 2026Reading the note…
4.3.1
22 Dec 2025Reading the note…
4.3.0
12 Dec 2025Only updates a dependency:@trigger.dev/core 4.3.0
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.