Global Flags
Global flags apply to every reactor command.
--context / -c
Section titled “--context / -c”Select which server context to use. Overrides REACTOR_CONTEXT and the manifest default.
reactor --context cloud deployreactor -c local functions list--manifest / -m
Section titled “--manifest / -m”Path to the project manifest. By default, Reactor searches the current directory and parents for reactor.toml.
reactor -m ./apps/my-app/reactor.toml deploy--output / -o
Section titled “--output / -o”Output format: human (default on TTY) or json (default when piped).
reactor --output json jobs list | jq '.[].name'Skip confirmation prompts. Also set via REACTOR_ASSUME_YES=1.
reactor --yes cloud projects delete my-project--verbose / -v
Section titled “--verbose / -v”Enable verbose logging for debugging.
reactor -v deploy--token
Section titled “--token”Provide an authentication token directly. Overrides the token stored in the active context.
reactor --token "$REACTOR_TOKEN" whoamiEnvironment variables
Section titled “Environment variables”| Variable | Equivalent flag | Description |
|---|---|---|
REACTOR_CONTEXT | --context | Default context name |
REACTOR_TOKEN | --token | Bearer token for API calls |
REACTOR_OUTPUT | --output | human or json |
REACTOR_ASSUME_YES | --yes | Set to 1 to skip prompts |
Context configuration
Section titled “Context configuration”Contexts are stored in ~/.reactor/config.toml. Add contexts with:
reactor context add cloud \ --endpoint https://api.reactor.cloud \ --org my-org
reactor context use cloudreactor login --browserExit codes
Section titled “Exit codes”| Code | Meaning |
|---|---|
0 | Success |
1 | General error |
2 | Invalid usage |