Skip to main content
This runs a server on your machine that can execute Trigger.dev tasks:
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.

​
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:
Then add something like this in your package.json scripts: