Packages

@trigger.dev/sdk

4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed

Your version

180 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.

  1. 4.8.8

    20 Nov 2026
    • The MCP list_runs tool can now filter runs by queue, batch, schedule and bulk action, and its descriptions now say that period takes precedence over from and to.

    • When OIDC token requests are still throttled after retries, auth.getOIDCToken() now throws RateLimitError with code RATE_LIMIT_EXCEEDED for both per-run and shared API limits. If you catch these errors with instanceof OIDCTokenError, check for RateLimitError instead. 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.

  2. 4.8.7

    19 Nov 2026
    • Sessions and chat.agent now accept the object form of concurrencyKey in triggerConfig, giving each concurrency limit its own key, the same as task.trigger().

    • Fix runs failing with TASK_DID_CONCURRENT_WAIT on their first wait when processKeepAlive is enabled.

    • Fix chat.agent channels 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's download, and on AI SDK 6 it reaches the model instead of failing the turn.

  3. 4.8.6

    18 Nov 2026
    • Allow an explicit audience when signing and verifying JWTs and user-actor tokens.

    • Deploys on the bun-1.4 runtime now compile the run worker and your task files into a Bun executable with bytecode, so runs start faster. import.meta.url and __dirname still point at your files under /app, so files you read next to your code must be in the image as before (e.g. with additionalFiles). Set build.bunBytecode: false in trigger.config.ts to turn compilation off.

    • trigger dev and trigger deploy no longer crash with spawn ... ENOENT on bun runtimes when Bun isn't installed at ~/.bun. The CLI now falls back to bun on your PATH (Homebrew, mise and similar installs), and if Bun still can't be started, trigger dev reports a readable error and trigger deploy skips local skill discovery with a warning and carries on.

  4. 4.8.5

    12 Nov 2026
    • Security

      Deployed tasks on the node, node-22, node-24 and node-26 runtimes 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.

  5. 4.8.4

    10 Nov 2026
    • 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 allow sts:TagSession before enabling them; existing integrations remain untagged.

    • Logins made with trigger.dev login or 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 with CLI_LOGIN_IDLE_TIMEOUT_DAYS, or set it to 0 to turn it off for new logins. Logins made before this change aren't affected.

    • Add infisicalAccessToken at @trigger.dev/sdk/oidc/infisical to authenticate tasks with Infisical using OIDC instead of stored credentials. Supports US, EU, and self-hosted instances, custom audiences, and Infisical organization scoping.

  6. 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 to runtime: "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-secret and trigger webhooks generate-secret, which store a webhook endpoint's signing secret without printing it. set-secret reads the secret from a pipe, an environment variable or a .env file, and generate-secret saves 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 24h in scripts). The MCP server's set_webhook_secret and generate_webhook_secret descriptions now point AI agents at these commands, so the secret stays out of the agent's context.

  7. 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 clickhouse event store is retired: task events now go to clickhouse_v2. If you self-host with EVENT_REPOSITORY_DEFAULT_STORE=clickhouse, switch it to clickhouse_v2 and follow the self-hosting guide to copy older events, which no longer show until you do.

    • Security

      Upgrade socket.io-client to 4.8.4 so projects using the SDK and CLI install ws 8.21 instead of 8.17.1, which has published advisories (GHSA-96hv-2xvq-fx4p, GHSA-58qx-3vcg-4xpx). The old pin blocked upgrading ws without a package manager override.

  8. 4.8.1

    23 Oct 2026
    • Fix trigger deploy failing 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.

  9. 4.8.0

    23 Oct 2026
    • Route verified webhooks into agent sessions with chat.event({ endpoint, key }), and connect external chat surfaces with chat.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 (errorMessage sets it, as a string or a function of the failure). Use chat.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 with webhook({ endpoint, filter, onEvent }), each with its own type-safe filter, and pause a run until a matching webhook arrives with webhooks.waiter.create() and webhooks.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) and webhooks.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 waiter match paths share the event., header. and webhook. namespaces, and filters accept == null / != null presence checks and event any (...) over a payload that is an array of events. webhook() takes task() options such as queue, machine and retry. 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_secret and set_webhook_secret MCP tools take an optional previousSecretTtlSeconds to 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.

  10. 4.7.7

    22 Oct 2026
    • Security

      Deployed tasks on the node, node-22, node-24 and node-26 runtimes 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.

  11. 4.7.6

    20 Oct 2026
    • Added MCP tools for monitoring alerts: list_alert_capabilities, list_alerts, create_alert, and resolve_alert, so an MCP client can discover what a project can watch and manage alerts directly. Health capabilities expose customizable threshold params, discoverable via list_alert_capabilities and settable via create_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_CERTS set as an environment variable now reaches the task process at startup instead of being overwritten by the image's empty default.

  12. 4.7.5

    20 Oct 2026
    • Add trigger.dev tasks trigger <task id> to trigger a task from your terminal. It uses the dev environment unless you pass --env, and --wait waits for the run and prints its output or error, exiting with code 1 if it failed. The runs commands now use the same dev branch as trigger dev when you pass --env dev.

      npx trigger.dev@latest tasks trigger hello-world --payload '{"name":"Ada"}' --wait
    • Manage custom metric dashboards from code. query.dashboards lists, creates, updates and deletes custom dashboards and their widgets, and every widget query is checked when it is saved. The MCP server adds create_dashboard and set_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 deploy and trigger promote now say which environment they're targeting, and accept --prod as a shorthand for --env prod. When TRIGGER_ACCESS_TOKEN holds an environment API key and you don't pass --env, they now use that key's environment instead of assuming prod. Passing an --env that 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 deploy tool no longer defaults to prod, so your AI assistant has to choose the environment.

  13. 4.7.4

    14 Oct 2026
    • Self-hosted instances can require custom deploy base images per runtime via the new DEPLOY_BASE_IMAGES and DEPLOY_BUILD_BASE_IMAGES webapp settings. The CLI builds on the images the instance specifies, and older CLIs are rejected with an upgrade message.

    • Add a replay_run tool 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 --readonly mode.

    • Override a concurrency limit's perKey for a single concurrencyKey: 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, and retrieve(name, { concurrencyKey }) shows the key's bound and when the override expires.

  14. 4.7.3

    6 Oct 2026
    • Breaking

      Creating or resuming a session with POST /api/v1/sessions now requires both session-write and task-trigger permissions. Scoped keys and public tokens must grant write: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 list to show the organizations you belong to, with their slugs and IDs. Use the slug with trigger.dev projects create --org, including for organizations that don't have any projects yet. trigger.dev projects create now activates the Free plan for organizations that don't have a plan yet, matching trigger.dev init.

  15. 4.7.2

    2 Oct 2026
    • Use the current Node.js LTS for deployments whose runtime is unset or set to "node". Set a versioned runtime such as "node-24" to keep deployments pinned to that Node.js major.

    • chat.agent now 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.agent response 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.

  16. 4.7.1

    2 Oct 2026
    • trigger.dev init now stops with a clear error when the target directory has no package.json, instead of installing packages into a parent project. A custom task directory entered during interactive init <path> is now written to trigger.config.ts relative to the project directory.

    • The CLI and MCP authorization page now shows the account and organizations you're granting access to.

  17. 4.7.0

    1 Oct 2026
    • Deprecated

      Deprecate queues.overrideConcurrencyLimit and queues.resetConcurrencyLimit. These operate on the legacy model where a queue carried its own concurrency limit; declare concurrency with the task concurrency option and manage it with concurrencyLimits.override and concurrencyLimits.reset instead.

    • Chat agents can now scope concurrency per session. Pass concurrencyKey (for example, your chat ID or tenant ID) and trigger-time named limits via triggerConfig.concurrency when starting a chat session, from chat.createStartSessionAction, the AgentChat client, 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, and concurrencyLimits.resume(name) starts them again.

      import { concurrencyLimits } from "@trigger.dev/sdk";
      
      await concurrencyLimits.pause("openai");
      await concurrencyLimits.resume("openai");
  18. 4.6.4

    22 Sep 2026

    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.

  19. 4.6.3

    17 Sep 2026
    • Show how to override the default cron window in schedule policy warnings.

    • Thrown error cause chains 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 error of API and realtime run records as a causes array, and triggerAndWait and triggerAndSubscribe rebuild it as a native cause on the error they hand back, so err.cause works 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.

  20. 4.6.2

    16 Sep 2026
    • 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 turnUsage on 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.

  21. 4.6.1

    15 Sep 2026
    • 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, and env set

    • Warn 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.

  22. 4.6.0

    14 Sep 2026
    • Breaking

      Minimum supported Zod version is now 3.25.56 released in June 2025. Trigger.dev now uses Zod 4 by default. Projects using Zod 3.25.56 or 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 .in channel (GET /realtime/v1/sessions/{id}/in and /in/records) now requires a secret key. Public tokens, including read:sessions:{id}, get a 403; they can still read .out and 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.

  23. 4.5.16

    2 Sep 2026
    • The trigger.dev deploy and trigger.dev dev commands now warn (with the suggested fix) when your code loads a package through createRequire() 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.

  24. 4.5.15

    31 Aug 2026
    • Stop shipping compiled test files in the published packages. The *.test.ts sources were being emitted into dist, adding dead weight to every install and leaving modules that require("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) (or chat.channel(name) inside a chat.agent) to get an .in/.out pair addressed by name rather than the reserved default pair. Writing a side channel's .in does 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, including useSessionStreamChannel in React. Channels get a default retention that keeps them bounded, overridable per channel.

    • Session triggerConfig.tags now accepts up to 10 tags, matching the run tag limit. Previously it was capped at 5, which for chat.agent left room for only 4 of your own tags after the automatic chat:{chatId} tag.

  25. 4.5.14

    28 Aug 2026
    • Native build server deploys now show a single updating build log line by default; pass --build-logs full to 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 refreshAccessToken option 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" to useRealtimeStream, streams.read(), or fetchStream to start at the current tail (the latest record, then live updates) instead of replaying (a live "last value" view), and maxParts to keep the accumulated parts array 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.

      useRealtimeStream also gains a lastEventId option and returns the lastEventId of the last part seen, so you can persist the cursor (for example across a page reload) and resume exactly where you left off. An onParts callback 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,
      });
  26. 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 deploy now asks the server whether to build with Depot or the native build server unless --native-build, --depot-build, or --local-build is passed, so the native build server can be rolled out per organization without a CLI change. --local-bundle and --detach now require --native-build.

    • Add an experimental --local-bundle deploy 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.

  27. 4.5.12

    20 Aug 2026
    • 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.

    • trigger.dev deploy --external-id tags 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 --force to rebuild it.

    • List the current Production runtime for every accessible project with trigger projects list. Add --needs-update to identify projects currently running Node.js 21.

  28. 4.5.11

    13 Aug 2026
    • Allow trigger deploy to authenticate with an environment API key from TRIGGER_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 json format, and the shortest report period is now one minute (1m, 30m, 1h, 7d). The mint-token command's help is clearer too: a token minted without --cap is read-only, and --ttl shows 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 init scaffold now imports from @trigger.dev/sdk instead of the deprecated @trigger.dev/sdk/v3 subpath.

  29. 4.5.10

    7 Aug 2026
    • 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/apiKeys now 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/typescript6 compatibility 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.

  30. 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 mcp now always starts the MCP server, and the interactive install wizard has moved behind trigger 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 health returns 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_report MCP tool, and GET /api/v1/reports/health all return the same text with the same sparklines. In MCP hosts that support prompts, report is also available as a slash command.

  31. 4.5.8

    27 Jul 2026
    • Preserve the partial assistant message when a chat turn's model stream fails mid-response. chat.agent now passes the recovered partial to onTurnComplete, and chat.createSession's turn.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.

  32. 4.5.7

    23 Jul 2026
    • Deprecated

      Add node-24 and node-26 as supported runtime options in trigger.config.ts. The experimental-node-24 and experimental-node-26 names are now deprecated aliases and emit a deprecation warning; switch to node-24 / node-26 instead.

      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 (lastEventId for the output stream and sessionInEventId for 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 a PipeAndCaptureResult whose message holds any partial output captured before the stop or failure, alongside a typed status ("complete" | "aborted" | "error") and, on failure, the error. 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: pipeAndCapture previously resolved to UIMessage | undefined. Update call sites to read .message from the returned result.

  33. 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=true to 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 the worker.id attribute, instead of an opaque internal value. Upgrade to get the readable identifier in your own OpenTelemetry exporters.

  34. 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 runtime to experimental-node-24 or experimental-node-26 in trigger.config.ts.

    • Add defaultRegion to the project GET and list API responses; null when unset.

  35. 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 --mcp and --mcp-port options from the dev command. Run the dedicated trigger mcp command to start the Trigger.dev MCP server.

    • You can now mark environment variables synced via the syncEnvVars build 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.

  36. 4.5.3

    10 Jul 2026
    • Breaking

      Removed support for the end-of-life v3 trigger dev CLI. Starting a dev session with an old v3 CLI now returns an upgrade message instead of connecting - upgrade to the v4 CLI to continue using trigger dev.

    • Fix TS2742 ("inferred type cannot be named") when exporting a chat.agent from a project with declaration emit: ChatTaskWirePayload and ChatInputChunk are now declared in the public @trigger.dev/sdk/chat subpath, 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.

  37. 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.

  38. 4.5.1

    6 Jul 2026
    • Extend the SSO plugin contract with WorkOS Directory Sync (SCIM) support.

  39. 4.5.0

    2 Jul 2026
    • 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)

  40. 4.4.6

    12 May 2026
    • Fail attempts on uncaught exceptions instead of hanging to MAX_DURATION_EXCEEDED. A Node EventEmitter (e.g. node-redis) emitting "error" with no .on("error", ...) listener escalates to uncaughtException, 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 status FAILED, 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 an uncaughtException feedback loop: a periodic IPC send via process.send would throw ERR_IPC_CHANNEL_CLOSED once the parent closed the channel, which re-entered the same handler that itself called process.send, scheduled via setImmediate and amplified by source-map-support's prepareStackTrace. Fixed by (1) silently dropping packets in ZodIpcConnection when the channel is disconnected, (2) adding a process.on("disconnect", ...) handler in dev workers so they exit cleanly when the CLI closes the IPC channel, and (3) wrapping all uncaughtException-path process.send calls in a safeSend guard that checks process.connected and swallows synchronous throws.

  41. 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-browser flag to init and login to skip auto-opening the browser during authentication. Also error loudly when init is run without --yes under non-TTY stdin (previously default-and-exited silently, leaving the project half-initialized). Both commands now show an Examples section in --help.

  42. 4.4.4

    13 Apr 2026
    • 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.

    • Add platform notifications support to the CLI. The trigger dev and trigger login commands 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-notifications flag with trigger dev to disable the notification check.

  43. 4.4.3

    10 Mar 2026

    Reading the note…

  44. 4.4.2

    4 Mar 2026

    Reading the note…

  45. 4.4.1

    20 Feb 2026

    Reading the note…

  46. 4.4.0

    19 Feb 2026
    • 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 via period or from/to ranges, and a format option 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
    • Add maxDelay option 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 getRunIdForOptions logic with the Core package to handle semantic targets (root, parent) in root tasks.

  47. 4.3.3

    23 Jan 2026

    Reading the note…

  48. 4.3.2

    8 Jan 2026

    Reading the note…

  49. 4.3.1

    22 Dec 2025

    Reading the note…

  50. 4.3.0

    12 Dec 2025

    Only 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.