GeezerVison

The World Wide Web, restored to 800 pixels of glory.

GeezerVison is showing trigger.dev — CLI dev command - Trigger.dev

This runs a server on your machine that can execute Trigger.dev tasks:

npx trigger.dev@latest dev

pnpm dlx trigger.dev@latest dev

yarn dlx trigger.dev@latest dev

It will first perform an update check to prevent version mismatches, failed deploys, and other errors. You will always be prompted first. You will see in the terminal that the server is running and listening for tasks. When you run a task, you will see it in the terminal along with a link to view it in the dashboard. It is worth noting that each task runs in a separate Node process. This means that if you have a long-running task, it will not block other tasks from running. When a build fails, the dev command keeps watching your files and rebuilds as soon as you fix the errors. Until then, new runs use the last version that built successfully.

Running dev from a coding agent

The dev command detects when a coding agent such as Claude Code, Cursor, Codex or Gemini CLI is running it, and changes its output so the agent can act on it:

It skips the prompts to install the MCP server and agent skills.
If your @trigger.dev/* packages don’t match the CLI version, it exits with instructions instead of asking whether to update them.
When the local worker is ready, it lists the task ids it registered and prints plain dashboard URLs.
Each run prints its dashboard URL, and successful runs print their output.

If your agent isn’t detected, set the AI_AGENT environment variable to its name. To test a task, an agent can trigger it with tasks trigger and --wait, which prints the run’s output or error.

Options

--config | -c

The name of the config file found at the project path. Defaults to trigger.config.ts

--project-ref | -p

The project ref. Required if there is no config file.

--env-file

Load environment variables from a file instead of the default .env files. They are available to your tasks in the local dev session.

--skip-update-check

Skip checking for @trigger.dev package updates.

--branch | -b

The dev branch to use. Defaults to the TRIGGER_DEV_BRANCH environment variable. See dev branches.

--max-concurrent-runs

The maximum number of concurrent runs in the dev session. It can only lower your dev environment’s concurrency limit, not raise it.

--keep-tmp-files

Keep temporary files after the dev session ends.

--analyze

Analyzes the build output and displays detailed import timings. This is useful for debugging the start times for your runs which can be caused by importing lots of code or heavy packages.

Common options

These options are available on most commands.

--profile

The login profile to use. Defaults to the current profile, which is set by your last login or switch (initially “default”).

--api-url | -a

Override the default API URL. If not specified, it uses https://api.trigger.dev. This can also be set via the TRIGGER_API_URL environment variable.

--log-level | -l

The CLI log level to use. Options are debug, info, log, warn, error, and none. This does not affect the log level of your trigger.dev tasks. Defaults to log.

--skip-telemetry

Opt-out of sending telemetry data. This can also be done via the TRIGGER_TELEMETRY_DISABLED environment variable. Just set it to anything other than an empty string.

--help | -h

Shows the help information for the command.

--version | -v

Displays the version number of the CLI.

Concurrently running the terminal

Install the concurrently package as a dev dependency:

concurrently --raw --kill-others npm:dev:remix npm:dev:trigger

Then add something like this in your package.json scripts:

"scripts": {
  "dev": "concurrently --raw --kill-others npm:dev:*",
  "dev:trigger": "npx trigger.dev@latest dev",
  // Add your framework-specific dev script here, for example:
  // "dev:next": "next dev",
  // "dev:remix": "remix dev",
  //...
}

Was this page helpful?

⌘I

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.

GeezerVison

​Running dev from a coding agent

​Options

​Common options

​Concurrently running the terminal

Running dev from a coding agent

Options

Common options

Concurrently running the terminal