prod. Use --env staging or --env preview (with --branch) for the other environments. There is no dev target: local trigger dev reads your local .env.
env list
Lists user-set environment variables.TRIGGER_ system variables are omitted. Values are hidden unless you pass --show-values.
env get
Prints one variable.--raw prints only the value, with no banner or extra text, so you can capture it in a script.
env set
Creates the variable if it does not exist, and overwrites the value if it does. Empty or whitespace-only values are rejected. Updating an existing secret without--secret changes the value and leaves it secret. Pass --secret when you first create a secret, or when you want a non-secret variable to become one.
env pull
Writes the project’s environment variables to a local file. Defaults to.env.local. Asks you to confirm before overwriting an existing file unless you pass --force. TRIGGER_ system variables are omitted.
Options
Required when using
--env preview. Specify the branch, e.g. --branch my-branch or -b my-branch.Common options
These options are available on most commands.The login profile to use. Defaults to the current profile, which is set by your last
login or switch (initially “default”).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.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.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.
