- Simple AI image generation. Receives prompt and parameters, calls OpenAI DALL·E 3, post-processes result, uploads to storage.
+ Simple AI image generation. Receives prompt and parameters, calls an image generation model, post-processes result, uploads to storage.
diff --git a/docs/images/environment-variables-page.jpg b/docs/images/environment-variables-page.jpg
index 21a6ac94b56..1da22f3469d 100644
Binary files a/docs/images/environment-variables-page.jpg and b/docs/images/environment-variables-page.jpg differ
diff --git a/docs/images/environment-variables-panel.jpg b/docs/images/environment-variables-panel.jpg
index 3dd3d642952..47686649052 100644
Binary files a/docs/images/environment-variables-panel.jpg and b/docs/images/environment-variables-panel.jpg differ
diff --git a/docs/images/replay-run-action.png b/docs/images/replay-run-action.png
index ea0a3eb15cd..a523acd7658 100644
Binary files a/docs/images/replay-run-action.png and b/docs/images/replay-run-action.png differ
diff --git a/docs/images/replay-run-modal.png b/docs/images/replay-run-modal.png
index f97494b724e..85e3c92ea11 100644
Binary files a/docs/images/replay-run-modal.png and b/docs/images/replay-run-modal.png differ
diff --git a/docs/images/replay-runs-list-popover.png b/docs/images/replay-runs-list-popover.png
index 7444225ac44..8585a3f4e12 100644
Binary files a/docs/images/replay-runs-list-popover.png and b/docs/images/replay-runs-list-popover.png differ
diff --git a/docs/images/replay-runs-list.png b/docs/images/replay-runs-list.png
index 8679520fbc8..5e414b4607f 100644
Binary files a/docs/images/replay-runs-list.png and b/docs/images/replay-runs-list.png differ
diff --git a/docs/images/run-log.png b/docs/images/run-log.png
index 7b695e5ed4d..9097f7f4f14 100644
Binary files a/docs/images/run-log.png and b/docs/images/run-log.png differ
diff --git a/docs/images/run-page.png b/docs/images/run-page.png
index aa895555be8..edbcc954d35 100644
Binary files a/docs/images/run-page.png and b/docs/images/run-page.png differ
diff --git a/docs/images/tags-filtering.png b/docs/images/tags-filtering.png
index 1b62503a274..a921ab34270 100644
Binary files a/docs/images/tags-filtering.png and b/docs/images/tags-filtering.png differ
diff --git a/docs/images/tags-org-user.png b/docs/images/tags-org-user.png
index a04d9e69b1c..0cae3cb34a7 100644
Binary files a/docs/images/tags-org-user.png and b/docs/images/tags-org-user.png differ
diff --git a/docs/images/terminal-completed-run.png b/docs/images/terminal-completed-run.png
index 805e32fda94..57bcc1901c9 100644
Binary files a/docs/images/terminal-completed-run.png and b/docs/images/terminal-completed-run.png differ
diff --git a/docs/images/trigger-cli-run-success.png b/docs/images/trigger-cli-run-success.png
index 76de17971a2..b4fa4d5e1c0 100644
Binary files a/docs/images/trigger-cli-run-success.png and b/docs/images/trigger-cli-run-success.png differ
diff --git a/docs/images/troubleshooting-alerts-blank.png b/docs/images/troubleshooting-alerts-blank.png
index e7f96a03a23..2d1e8f008e7 100644
Binary files a/docs/images/troubleshooting-alerts-blank.png and b/docs/images/troubleshooting-alerts-blank.png differ
diff --git a/docs/images/troubleshooting-alerts-disable-delete.png b/docs/images/troubleshooting-alerts-disable-delete.png
index bf64de5516d..8927d58e0f6 100644
Binary files a/docs/images/troubleshooting-alerts-disable-delete.png and b/docs/images/troubleshooting-alerts-disable-delete.png differ
diff --git a/docs/images/troubleshooting-alerts-modal.png b/docs/images/troubleshooting-alerts-modal.png
index 357185ff509..5a1e390e816 100644
Binary files a/docs/images/troubleshooting-alerts-modal.png and b/docs/images/troubleshooting-alerts-modal.png differ
diff --git a/docs/introduction.mdx b/docs/introduction.mdx
index 50d4cd80785..951c7567172 100644
--- a/docs/introduction.mdx
+++ b/docs/introduction.mdx
@@ -15,7 +15,7 @@ import AgentSetupPrompt from "/snippets/agent-setup-prompt.mdx";
Durable, multi-turn agents with `chat.agent`, from your frontend to Slack and Linear.
- Let Claude Code, Cursor and Windsurf write correct Trigger.dev code with the MCP server, Skills and rules.
+ Let Claude Code, Codex, Cursor and other coding agents write correct Trigger.dev code with the MCP server, Skills and rules.
Frameworks like Next.js, worked example projects, and step-by-step how-to guides.
diff --git a/docs/mcp-introduction.mdx b/docs/mcp-introduction.mdx
index f9d2b39c5c8..744a208245b 100644
--- a/docs/mcp-introduction.mdx
+++ b/docs/mcp-introduction.mdx
@@ -57,36 +57,32 @@ Each client has a slightly different config format. Copy the snippet for your cl
[View Claude Code MCP docs ↗](https://code.claude.com/docs/en/mcp)
-
+
Install using the command line:
```bash
- npx trigger.dev@latest install-mcp --client cursor
+ npx trigger.dev@latest install-mcp --client openai-codex
```
- Or add this configuration to `~/.cursor/mcp.json` (user) or `.cursor/mcp.json` (project):
+ Or add this configuration to `~/.codex/config.toml`:
- ```json
- {
- "mcpServers": {
- "trigger": {
- "command": "npx",
- "args": ["trigger.dev@latest", "mcp"]
- }
- }
- }
+ ```toml
+ [mcp_servers.trigger]
+ command = "npx"
+ args = ["trigger.dev@latest", "mcp"]
+ startup_timeout_sec = 30
```
- [View Cursor MCP docs ↗](https://cursor.com/docs/context/mcp)
+ The `startup_timeout_sec = 30` is recommended. Codex defaults to 10 seconds, which may not be enough for `npx` to download the package on first run.
-
+
Install using the command line:
```bash
- npx trigger.dev@latest install-mcp --client windsurf
+ npx trigger.dev@latest install-mcp --client cursor
```
- Or add this configuration to `~/.codeium/windsurf/mcp_config.json`:
+ Or add this configuration to `~/.cursor/mcp.json` (user) or `.cursor/mcp.json` (project):
```json
{
@@ -99,7 +95,7 @@ Each client has a slightly different config format. Copy the snippet for your cl
}
```
- [View Windsurf MCP docs ↗](https://docs.windsurf.com/windsurf/cascade/mcp)
+ [View Cursor MCP docs ↗](https://cursor.com/docs/context/mcp)
Install using the command line:
@@ -125,72 +121,73 @@ Each client has a slightly different config format. Copy the snippet for your cl
[View VS Code MCP docs ↗](https://code.visualstudio.com/docs/copilot/chat/mcp-servers)
-
+
Install using the command line:
```bash
- npx trigger.dev@latest install-mcp --client zed
+ npx trigger.dev@latest install-mcp --client gemini-cli
```
- Or add this configuration to `~/.config/zed/settings.json`:
+ Or add this configuration to `~/.gemini/settings.json` (user) or `.gemini/settings.json` (project):
```json
{
- "context_servers": {
+ "mcpServers": {
"trigger": {
- "source": "custom",
"command": "npx",
"args": ["trigger.dev@latest", "mcp"]
}
}
}
```
-
- [View Zed context servers docs ↗](https://zed.dev/docs/ai/mcp)
-
+
Install using the command line:
```bash
- npx trigger.dev@latest install-mcp --client cline
+ npx trigger.dev@latest install-mcp --client opencode
```
- Or add this configuration to `~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`:
+ Or add this configuration to `~/.config/opencode/opencode.json` (user) or `./opencode.json` (project):
```json
{
- "mcpServers": {
+ "mcp": {
"trigger": {
- "command": "npx",
- "args": ["trigger.dev@latest", "mcp"]
+ "type": "local",
+ "command": ["npx", "trigger.dev@latest", "mcp"],
+ "enabled": true
}
}
}
```
- [View Cline MCP docs ↗](https://docs.cline.bot/mcp/configuring-mcp-servers)
+ [View opencode MCP docs ↗](https://opencode.ai/docs/mcp-servers/)
-
+
Install using the command line:
```bash
- npx trigger.dev@latest install-mcp --client gemini-cli
+ npx trigger.dev@latest install-mcp --client zed
```
- Or add this configuration to `~/.gemini/settings.json` (user) or `.gemini/settings.json` (project):
+ Or add this configuration to `~/.config/zed/settings.json`:
```json
{
- "mcpServers": {
+ "context_servers": {
"trigger": {
+ "source": "custom",
"command": "npx",
"args": ["trigger.dev@latest", "mcp"]
}
}
}
```
+
+ [View Zed context servers docs ↗](https://zed.dev/docs/ai/mcp)
-
+
Install using the command line:
```bash
@@ -210,40 +207,37 @@ Each client has a slightly different config format. Copy the snippet for your cl
}
```
- [View Sourcegraph AMP MCP docs ↗](https://ampcode.com/manual#mcp)
+ [View Amp MCP docs ↗](https://ampcode.com/manual#mcp)
-
+
Install using the command line:
```bash
- npx trigger.dev@latest install-mcp --client openai-codex
+ npx trigger.dev@latest install-mcp --client cline
```
- Or add this configuration to `~/.codex/config.toml`:
+ Or add this configuration to `~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json`:
- ```toml
- [mcp_servers.trigger]
- command = "npx"
- args = ["trigger.dev@latest", "mcp"]
- startup_timeout_sec = 30
+ ```json
+ {
+ "mcpServers": {
+ "trigger": {
+ "command": "npx",
+ "args": ["trigger.dev@latest", "mcp"]
+ }
+ }
+ }
```
- The `startup_timeout_sec = 30` is recommended. Codex defaults to 10 seconds, which may not be enough for `npx` to download the package on first run.
+ [View Cline MCP docs ↗](https://docs.cline.bot/mcp/configuring-mcp-servers)
-
- Install using the command line:
-
- ```bash
- npx trigger.dev@latest install-mcp --client crush
- ```
-
- Or add this configuration to `.crush.json` (project), `crush.json`, or `~/.config/crush/crush.json` (user). Files are loaded in priority order: `.crush.json` → `crush.json` → `$HOME/.config/crush/crush.json`.
+
+ Add this configuration to `~/.config/devin/mcp_config.json`, or to `.devin/mcp_config.json` in your project to share it with your team:
```json
{
- "mcp": {
+ "mcpServers": {
"trigger": {
- "type": "stdio",
"command": "npx",
"args": ["trigger.dev@latest", "mcp"]
}
@@ -251,30 +245,30 @@ Each client has a slightly different config format. Copy the snippet for your cl
}
```
- [View Charm MCP docs ↗](https://github.com/charmbracelet/crush)
+ [View Devin Desktop MCP docs ↗](https://docs.devin.ai/desktop/devin-local/customizations)
-
+
Install using the command line:
```bash
- npx trigger.dev@latest install-mcp --client opencode
+ npx trigger.dev@latest install-mcp --client crush
```
- Or add this configuration to `~/.config/opencode/opencode.json` (user) or `./opencode.json` (project):
+ Or add this configuration to `.crush.json` (project), `crush.json`, or `~/.config/crush/crush.json` (user). Files are loaded in priority order: `.crush.json` → `crush.json` → `$HOME/.config/crush/crush.json`.
```json
{
"mcp": {
"trigger": {
- "type": "local",
- "command": ["npx", "trigger.dev@latest", "mcp"],
- "enabled": true
+ "type": "stdio",
+ "command": "npx",
+ "args": ["trigger.dev@latest", "mcp"]
}
}
}
```
- [View opencode MCP docs ↗](https://opencode.ai/docs/mcp-servers/)
+ [View Charm MCP docs ↗](https://github.com/charmbracelet/crush)
Install using the command line:
diff --git a/docs/migration-mergent.mdx b/docs/migration-mergent.mdx
index 1d43dee8c06..b07d29ea54e 100644
--- a/docs/migration-mergent.mdx
+++ b/docs/migration-mergent.mdx
@@ -2,6 +2,7 @@
title: "Migrating from Mergent"
description: "A guide for migrating from Mergent to Trigger.dev"
sidebarTitle: "Migrating from Mergent"
+hidden: true
---
Mergent was acquired by Resend and its service shut down on July 28, 2025. If you ran background jobs or scheduled tasks on Mergent, you need to move them to another platform. Trigger.dev is a modern, developer-friendly platform for background jobs, workflows, and scheduling.
diff --git a/docs/quick-start.mdx b/docs/quick-start.mdx
index 97798be150f..f8c4cf47b75 100644
--- a/docs/quick-start.mdx
+++ b/docs/quick-start.mdx
@@ -1,7 +1,7 @@
---
title: "Quick start: add Trigger.dev to your project"
sidebarTitle: "Quick start"
-description: "Set up Trigger.dev in your existing project in under 3 minutes. Install the SDK, create your first background task, and trigger it from your code."
+description: "Set up Trigger.dev in your existing project in under 3 minutes. Install the SDK, create your first task, and trigger it from your code."
---
import CliInitStep from "/snippets/step-cli-init.mdx";
diff --git a/docs/realtime/overview.mdx b/docs/realtime/overview.mdx
index 94cd48c5b82..df6309d484f 100644
--- a/docs/realtime/overview.mdx
+++ b/docs/realtime/overview.mdx
@@ -1,7 +1,7 @@
---
title: Realtime overview
sidebarTitle: Overview
-description: "Get live run updates and stream data from background tasks to your frontend or backend. No polling."
+description: "Get live run updates and stream data from your tasks and agents to your frontend or backend. No polling."
---
**Realtime is the umbrella for everything live in Trigger.dev.** It covers two things: getting notified when a run's state changes, and streaming continuous data (like AI tokens) from a running task to your app.
diff --git a/docs/realtime/react-hooks/overview.mdx b/docs/realtime/react-hooks/overview.mdx
index 3d5a3f15788..80278575410 100644
--- a/docs/realtime/react-hooks/overview.mdx
+++ b/docs/realtime/react-hooks/overview.mdx
@@ -1,12 +1,12 @@
---
title: "React hooks for real-time task updates"
sidebarTitle: Overview
-description: "Subscribe to background task progress, stream AI responses, and trigger tasks from React components using @trigger.dev/react-hooks."
+description: "Subscribe to run progress, stream AI responses, and trigger tasks from React components using @trigger.dev/react-hooks."
---
import RealtimeExamplesCards from "/snippets/realtime-examples-cards.mdx";
-**`@trigger.dev/react-hooks` gives your React components live access to background tasks.** Subscribe to run progress, stream AI output as it generates, or trigger tasks directly from the browser.
+**`@trigger.dev/react-hooks` gives your React components live access to your runs.** Subscribe to run progress, stream AI output as it generates, or trigger tasks directly from the browser.
## Installation
diff --git a/docs/realtime/react-hooks/streams.mdx b/docs/realtime/react-hooks/streams.mdx
index ee6a8bd7cb6..816b01cb29f 100644
--- a/docs/realtime/react-hooks/streams.mdx
+++ b/docs/realtime/react-hooks/streams.mdx
@@ -1,7 +1,7 @@
---
title: "Stream data to React (AI, files, progress)"
sidebarTitle: "Streaming"
-description: "Display AI/LLM output token by token, stream file chunks, or pipe any continuous data from a background task into your React components."
+description: "Display AI/LLM output token by token, stream file chunks, or pipe any continuous data from a task into your React components."
---
**Display AI responses as they generate, stream file processing results, or pipe any continuous data from a running task into your React components.** Unlike [progress and status hooks](/realtime/react-hooks/subscribe) (which track run state), streaming hooks give you the raw data your task produces while it runs.
diff --git a/docs/realtime/react-hooks/subscribe.mdx b/docs/realtime/react-hooks/subscribe.mdx
index 5d207ffb358..80ed0e219f8 100644
--- a/docs/realtime/react-hooks/subscribe.mdx
+++ b/docs/realtime/react-hooks/subscribe.mdx
@@ -1,10 +1,10 @@
---
title: "Run updates in React"
sidebarTitle: "Run updates"
-description: "Build progress bars, status indicators, and live dashboards by subscribing to background task updates from React components."
+description: "Build progress bars, status indicators, and live dashboards by subscribing to run updates from React components."
---
-**Subscribe to a run and your component re-renders whenever its status, metadata, or tags change.** Build progress bars, deployment monitors, or any UI that needs to reflect what a background task is doing right now.
+**Subscribe to a run and your component re-renders whenever its status, metadata, or tags change.** Build progress bars, deployment monitors, or any UI that needs to reflect what a run is doing right now.
For streaming continuous data (AI tokens, file chunks), see [Streaming](/realtime/react-hooks/streams) instead.
diff --git a/docs/realtime/react-hooks/triggering.mdx b/docs/realtime/react-hooks/triggering.mdx
index ad7513f7cef..dadc9b130ad 100644
--- a/docs/realtime/react-hooks/triggering.mdx
+++ b/docs/realtime/react-hooks/triggering.mdx
@@ -1,7 +1,7 @@
---
title: "Trigger tasks from React"
sidebarTitle: Triggering
-description: "Trigger background tasks from React components and optionally subscribe to their progress or stream their output."
+description: "Trigger tasks from React components and optionally subscribe to their progress or stream their output."
---
Trigger tasks directly from your React components. You can fire-and-forget, or trigger and immediately subscribe to the run's progress or streamed output.
diff --git a/docs/replaying.mdx b/docs/replaying.mdx
index bd37181aefa..17869292da5 100644
--- a/docs/replaying.mdx
+++ b/docs/replaying.mdx
@@ -9,14 +9,12 @@ description: "A replay is a copy of a run with the same payload but against the
- 
+ 
You can edit the payload (if available) and choose the environment to replay the run in.
- 
+ 
diff --git a/docs/self-hosting/docker.mdx b/docs/self-hosting/docker.mdx
index 1062a2ea08f..db3b0c28194 100644
--- a/docs/self-hosting/docker.mdx
+++ b/docs/self-hosting/docker.mdx
@@ -11,20 +11,18 @@ Should the burden ever get too much, we'd be happy to see you on [Trigger.dev cl
**Warning:** This guide alone is unlikely to result in a production-ready deployment. Security, scaling, and reliability concerns are not fully addressed here.
-## What's new?
-
-Goodbye v3, hello v4! We made quite a few changes:
-
-- **Much simpler setup.** The provider and coordinator are now combined into a single supervisor. No more startup scripts, just `docker compose up`.
-- **Automatic container cleanup.** The supervisor will automatically clean up containers that are no longer needed.
-- **Support for multiple worker machines.** This is a big one, and we're very excited about it! You can now scale your workers horizontally as needed.
-- **Resource limits enforced by default.** This means that tasks will be limited to the total CPU and RAM of the machine preset, preventing noisy neighbours.
-- **No direct Docker socket access.** The compose file now comes with [Docker Socket Proxy](https://github.com/Tecnativa/docker-socket-proxy) by default. Yes, you want this.
-- **No host networking.** All containers are now running with network isolation, using only the network access they need.
-- **No checkpoint support.** This was only ever experimental when self-hosting and not recommended. It caused a bunch of issues. We decided to focus on the core features instead.
-- **Built-in container registry and object storage.** You can now deploy and execute tasks without needing third party services for this.
-- **Improved CLI commands.** You don't need any additional flags to deploy anymore, and there's a new command to easily `switch` between profiles.
-- **Whitelisting for GitHub OAuth.** Any whitelisted email addresses will now also apply to sign ins via GitHub, unlike v3 where they only applied to magic links.
+## What's included
+
+- **Single supervisor.** The supervisor manages worker containers, so there are no startup scripts: just `docker compose up`.
+- **Automatic container cleanup.** The supervisor cleans up containers that are no longer needed.
+- **Multiple worker machines.** You can scale your workers horizontally as needed.
+- **Resource limits enforced by default.** Tasks are limited to the total CPU and RAM of their machine preset, preventing noisy neighbours.
+- **No direct Docker socket access.** The compose file comes with [Docker Socket Proxy](https://github.com/Tecnativa/docker-socket-proxy) by default.
+- **No host networking.** All containers run with network isolation, using only the network access they need.
+- **No checkpoint support.** Checkpoints are not available when self-hosting.
+- **Built-in container registry and object storage.** You can deploy and execute tasks without third party services for these.
+- **Simple CLI setup.** You don't need any additional flags to deploy, and you can `switch` between profiles.
+- **Whitelisting for GitHub OAuth.** Whitelisted email addresses apply to sign ins via GitHub as well as magic links.
## Requirements
diff --git a/docs/snippets/realtime-examples-cards.mdx b/docs/snippets/realtime-examples-cards.mdx
index c7530849452..3a03d80e638 100644
--- a/docs/snippets/realtime-examples-cards.mdx
+++ b/docs/snippets/realtime-examples-cards.mdx
@@ -1,14 +1,6 @@
## Examples
-
- A chatbot using the AI SDK that demonstrates Anthropic Claude 3.7's thinking capabilities through the Realtime API and
- react hooks.
-