# Trigger.dev v4.5.11 — trigger.dev v4.5.11

- Product: Trigger.dev (https://whatsnew.fyi/product/trigger-dev)
- Vendor: Trigger.dev
- Date: 2026-08-13
- Version: v4.5.11
- Original notes: https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.11
- Permalink: https://whatsnew.fyi/product/trigger-dev/releases/v4.5.11

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **added** — Allow trigger deploy to authenticate with an environment API key from TRIGGER_ACCESS_TOKEN
- **added** — Chat in the browser now reconnects when the connection drops mid-turn instead of leaving the reply stuck as if it were still generating
- **added** — Reports can be fetched as structured data with the json format
- **changed** — The shortest report period is now one minute (1m, 30m, 1h, 7d)
- **changed** — The mint-token command's help is clearer with --cap showing read-only behavior and --ttl showing the correct maximum lifetime of 7 days
- **added** — Dev environment onboarding now tracks real progress with live updates as the dev server connects and tasks register
- **added** — Setup checklist marks the project as initialized after running init
- **added** — Blank state adds a Copy AI agent prompt button that copies a ready-to-paste setup prompt pre-filled with your project reference
- **changed** — The init scaffold now imports from @trigger.dev/sdk instead of the deprecated @trigger.dev/sdk/v3 subpath
- **changed** — Deployed images now ship dependencies and bundled task code as separate layers for faster deploys and worker image pulls
- **added** — The current-worker API now reports each task's queue so you can see which tasks write to a given queue
- **fixed** — Watch-mode chat streams now survive quiet windows and page reloads
- **fixed** — A reply cut off by a lost connection now shows an error instead of appearing finished
- **added** — Dashboard agent now has a monthly message allowance and plan-based limits on watches
- **added** — Introduced dashboard agent: a chat in every environment that answers questions about runs, queues, errors and health with real data and links
- **added** — Watch functionality on runs, queues, errors or health reports tells you when things change with notifications by email, Slack or webhook
- **added** — Queue wait times, peak depth, throughput and throttling can now be read from the API
- **added** — Add backend support for delaying cron schedules within a specified window with a minimum of 60 seconds
- **changed** — Reduced recurring background database load from the billing-limit recovery check so paused environments are reconciled with less overhead
- **fixed** — Project pages now load faster for projects with a large number of preview branches by no longer loading archived branch environments

#### trigger.dev v4.5.11

##### Upgrade

```sh
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.11`](https://github.com/triggerdotdev/trigger.dev/pkgs/container/trigger.dev/1129637572?tag=v4.5.11)

##### Release notes

Read the full release notes: https://trigger.dev/changelog/v4-5-11

##### What's changed

##### Highlights

- Allow `trigger deploy` to authenticate with an environment API key from `TRIGGER_ACCESS_TOKEN`. ([#4561](https://github.com/triggerdotdev/trigger.dev/pull/4561))

##### 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 `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. ([#4418](https://github.com/triggerdotdev/trigger.dev/pull/4418))
- 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. ([#4563](https://github.com/triggerdotdev/trigger.dev/pull/4563))
  
  The `init` scaffold now imports from `@trigger.dev/sdk` instead of the deprecated `@trigger.dev/sdk/v3` subpath.
- 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. ([#4551](https://github.com/triggerdotdev/trigger.dev/pull/4551))
- The current-worker API now reports each task's queue, so you can see which tasks write to a given queue. ([#4525](https://github.com/triggerdotdev/trigger.dev/pull/4525))
- 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 pass `stopOnAbort: true` to 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. ([#4516](https://github.com/triggerdotdev/trigger.dev/pull/4516))

##### 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. ([#4516](https://github.com/triggerdotdev/trigger.dev/pull/4516))
- 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 a

_[Truncated at 4000 characters — full notes: https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.11]_