Command Reference
Every reactor command accepts global flags (--context, --manifest, --output, --yes, --verbose, --token). Examples below omit them unless relevant.
Project lifecycle
Section titled “Project lifecycle”reactor init <NAME> [--force]Initialize a new Reactor project with a reactor.toml manifest and starter layout.
| Flag | Description |
|---|---|
--force | Overwrite existing files in the target directory |
Example
reactor init my-appreactor init my-app --forceproject show
Section titled “project show”reactor project showDisplay the active project manifest, resolved paths, and configuration summary.
| Flag | Description |
|---|---|
| (none) | No additional flags |
Example
reactor project showreactor -m ./apps/api/reactor.toml project showreactor build [--out <PATH>]Build a deployment bundle from the current project manifest.
| Flag | Description |
|---|---|
--out | Output path for the bundle (default: project-defined) |
Example
reactor buildreactor build --out ./dist/bundle.tar.gzdeploy
Section titled “deploy”reactor deploy [--bundle <PATH>] [--prebuilt]Deploy the project to the server configured in the active context.
| Flag | Description |
|---|---|
--bundle | Path to a pre-built bundle to upload |
--prebuilt | Skip building; use an existing bundle artifact |
Example
reactor deployreactor build --out ./bundle.tar.gz && reactor deploy --bundle ./bundle.tar.gzreactor deploy --prebuiltmigrate
Section titled “migrate”reactor migrate [--dry-run]Apply pending database schema migrations for the project.
| Flag | Description |
|---|---|
--dry-run | Show the migration plan without applying changes |
Example
reactor migrate --dry-runreactor migratedoctor
Section titled “doctor”reactor doctorRun diagnostics on the local project setup and remote server connectivity.
| Flag | Description |
|---|---|
| (none) | No additional flags |
Example
reactor doctorreactor -v doctorversion
Section titled “version”reactor versionPrint CLI version and build metadata.
| Flag | Description |
|---|---|
| (none) | No additional flags |
Example
reactor versionContext & auth
Section titled “Context & auth”context list
Section titled “context list”reactor context listList all configured server contexts from ~/.reactor/config.toml.
Example
reactor context listcontext add
Section titled “context add”reactor context add <NAME> --endpoint <URL> [--org <SLUG>] [--token <TOKEN>] [--token-env <VAR>]Add a new server context.
| Flag | Description |
|---|---|
--endpoint | Server endpoint URL (required) |
--org | Organization slug |
--token | Authentication token (conflicts with --token-env) |
--token-env | Environment variable containing the token (conflicts with --token) |
Example
reactor context add cloud --endpoint https://api.reactor.cloud --org acmereactor context add local --endpoint http://127.0.0.1:8080 --token-env REACTOR_LOCAL_TOKENcontext use
Section titled “context use”reactor context use <NAME>Set the default context for subsequent commands.
Example
reactor context use cloudcontext show
Section titled “context show”reactor context show [<NAME>]Show details for a context. Defaults to the active context when NAME is omitted.
Example
reactor context showreactor context show cloudcontext remove
Section titled “context remove”reactor context remove <NAME>Remove a stored context.
Example
reactor context remove stagingreactor login [--context <NAME>] [--token <TOKEN>] [--browser] [--no-browser] [--bootstrap] [--file-storage]Authenticate with a Reactor server. Browser PKCE OAuth is recommended for operators.
| Flag | Description |
|---|---|
--context | Context to authenticate (default: active context) |
--token | Store a token directly (legacy mode) |
--browser | Use browser-based PKCE OAuth flow |
--no-browser | Use device code flow instead of browser (requires --browser) |
--bootstrap | Bootstrap as the first platform operator (loopback + admin token) |
--file-storage | Store tokens in ~/.reactor/tokens.toml instead of OS keychain |
Example
reactor login --browserreactor login --context cloud --browser --no-browserreactor login --token "$REACTOR_TOKEN"logout
Section titled “logout”reactor logout [--context <NAME>]Remove stored authentication for a context.
| Flag | Description |
|---|---|
--context | Context to log out from (default: active context) |
Example
reactor logoutreactor logout --context cloudwhoami
Section titled “whoami”reactor whoamiShow the current authenticated user and organization.
Example
reactor whoamireactor --output json whoamiFunctions
Section titled “Functions”functions list
Section titled “functions list”reactor functions listList all functions defined in the project.
Example
reactor functions listfunctions show
Section titled “functions show”reactor functions show <NAME>Show details for a single function, including runtime and deployment status.
Example
reactor functions show send-emailfunctions deploy
Section titled “functions deploy”reactor functions deploy <NAME> [--source <DIR>]Deploy or redeploy a function.
| Flag | Description |
|---|---|
--source | Source directory (default: manifest path) |
Example
reactor functions deploy send-emailreactor functions deploy send-email --source ./functions/send-emailfunctions rollback
Section titled “functions rollback”reactor functions rollback <NAME> --to <DEPLOYMENT_ID>Roll back a function to a previous deployment.
| Flag | Description |
|---|---|
--to | Deployment ID to roll back to (required) |
Example
reactor functions rollback send-email --to dep_abc123functions invoke
Section titled “functions invoke”reactor functions invoke <NAME> [--data <JSON|@file.json>]Invoke a function with optional JSON payload.
| Flag | Description |
|---|---|
--data | Request body as JSON string or @file.json |
Example
reactor functions invoke send-email --data '{"to":"user@example.com"}'reactor functions invoke send-email --data @payload.jsonfunctions env list
Section titled “functions env list”reactor functions env list <NAME>List environment variables for a function.
Example
reactor functions env list send-emailfunctions env get
Section titled “functions env get”reactor functions env get <NAME> <KEY>Get a single environment variable value.
Example
reactor functions env get send-email SMTP_HOSTfunctions env set
Section titled “functions env set”reactor functions env set <NAME> <KEY> <VALUE>Set an environment variable on a function.
Example
reactor functions env set send-email SMTP_HOST smtp.example.comfunctions env unset
Section titled “functions env unset”reactor functions env unset <NAME> <KEY>Remove an environment variable from a function.
Example
reactor functions env unset send-email SMTP_HOSTfunctions logs
Section titled “functions logs”reactor functions logs <NAME> [--since <DURATION>] [-f|--follow]View logs for a function.
| Flag | Description |
|---|---|
--since | Show logs since a duration (e.g., 1h, 30m) |
-f, --follow | Follow logs via polling |
Example
reactor functions logs send-email --since 1hreactor functions logs send-email -fsites list
Section titled “sites list”reactor sites listList all sites in the project.
Example
reactor sites listsites show
Section titled “sites show”reactor sites show <NAME>Show site details, deployment history, and domain configuration.
Example
reactor sites show websites deploy
Section titled “sites deploy”reactor sites deploy <NAME> [--source <DIR>]Deploy a site.
| Flag | Description |
|---|---|
--source | Source directory (default: manifest path) |
Example
reactor sites deploy webreactor sites deploy web --source ./apps/web/distsites promote
Section titled “sites promote”reactor sites promote <NAME> --deployment <DEPLOYMENT_ID>Promote a specific deployment to production traffic.
| Flag | Description |
|---|---|
--deployment | Deployment ID to promote (required) |
Example
reactor sites promote web --deployment dep_xyz789sites rollback
Section titled “sites rollback”reactor sites rollback <NAME>Roll back a site to the previous deployment.
Example
reactor sites rollback websites domains list
Section titled “sites domains list”reactor sites domains list <NAME>List custom domains attached to a site.
Example
reactor sites domains list websites domains add
Section titled “sites domains add”reactor sites domains add <NAME> <DOMAIN>Add a custom domain to a site.
Example
reactor sites domains add web app.example.comsites domains remove
Section titled “sites domains remove”reactor sites domains remove <NAME> <DOMAIN_ID>Remove a custom domain from a site.
Example
reactor sites domains remove web dom_abc123sites domains verify
Section titled “sites domains verify”reactor sites domains verify <NAME> <DOMAIN_ID>Trigger DNS verification for a pending domain.
Example
reactor sites domains verify web dom_abc123sites revalidate
Section titled “sites revalidate”reactor sites revalidate <NAME> --path <PATH>Revalidate ISR cache for a specific path.
| Flag | Description |
|---|---|
--path | Path to revalidate (required) |
Example
reactor sites revalidate web --path /blog/my-postsites logs
Section titled “sites logs”reactor sites logs <NAME> [--since <DURATION>]View logs for a site.
| Flag | Description |
|---|---|
--since | Show logs since a duration (e.g., 1h, 30m) |
Example
reactor sites logs web --since 30mjobs list
Section titled “jobs list”reactor jobs listList all background jobs defined in the project.
Example
reactor jobs listjobs show
Section titled “jobs show”reactor jobs show <NAME>Show job configuration and schedule details.
Example
reactor jobs show nightly-syncjobs trigger
Section titled “jobs trigger”reactor jobs trigger <NAME> [--data <JSON|@file.json>]Manually trigger a job run.
| Flag | Description |
|---|---|
--data | Job payload as JSON string or @file.json |
Example
reactor jobs trigger nightly-syncreactor jobs trigger nightly-sync --data '{"full":true}'jobs runs
Section titled “jobs runs”reactor jobs runs <NAME> [--limit <N>]List recent runs for a job.
| Flag | Description |
|---|---|
--limit | Maximum number of runs to show |
Example
reactor jobs runs nightly-sync --limit 10jobs run
Section titled “jobs run”reactor jobs run <RUN_ID>Show details for a specific job run.
Example
reactor jobs run run_abc123jobs dlq list
Section titled “jobs dlq list”reactor jobs dlq list [--job <NAME>]List dead letter queue entries.
| Flag | Description |
|---|---|
--job | Filter by job name |
Example
reactor jobs dlq listreactor jobs dlq list --job nightly-syncjobs dlq replay
Section titled “jobs dlq replay”reactor jobs dlq replay <ID>Replay a DLQ entry back into the job queue.
Example
reactor jobs dlq replay dlq_abc123jobs dlq purge
Section titled “jobs dlq purge”reactor jobs dlq purge [--job <NAME>]Purge DLQ entries, optionally filtered by job name.
| Flag | Description |
|---|---|
--job | Filter purge to a specific job |
Example
reactor jobs dlq purge --job nightly-syncjobs logs
Section titled “jobs logs”reactor jobs logs <NAME> [--since <DURATION>]View logs for a job.
| Flag | Description |
|---|---|
--since | Show logs since a duration |
Example
reactor jobs logs nightly-sync --since 2hdata migrate
Section titled “data migrate”reactor data migrate [--dry-run]Run data-layer migrations (distinct from schema migrate).
| Flag | Description |
|---|---|
--dry-run | Show migration plan without applying |
Example
reactor data migrate --dry-runreactor data migratedata inspect
Section titled “data inspect”reactor data inspect <TABLE>Inspect table schema, row counts, and sample metadata.
Example
reactor data inspect usersdata query
Section titled “data query”reactor data query --sql <SQL> [--params <JSON|@file.json>] [--write]Execute a SQL query against the project database.
| Flag | Description |
|---|---|
--sql | SQL query string (required) |
--params | Query parameters as JSON or @file.json |
--write | Allow write operations (INSERT, UPDATE, DELETE) |
Example
reactor data query --sql "SELECT id, email FROM users LIMIT 5"reactor data query --sql "UPDATE users SET active = $1 WHERE id = $2" \ --params '["true","usr_123"]' --writeai models
Section titled “ai models”reactor ai models [-c|--capability <CAPABILITY>]List available AI models, optionally filtered by capability.
| Flag | Description |
|---|---|
-c, --capability | Filter by capability (chat, reasoning, vision, embeddings, etc.) |
Example
reactor ai modelsreactor ai models --capability chatai aliases
Section titled “ai aliases”reactor ai aliasesList configured model aliases for the project.
Example
reactor ai aliasesai test
Section titled “ai test”reactor ai test <MODEL> [-p|--prompt <TEXT>] [-s|--system <TEXT>] [--stream] [--max-tokens <N>]Send a test prompt to a model or alias.
| Flag | Description |
|---|---|
-p, --prompt | Prompt to send |
-s, --system | System message |
--stream | Enable streaming output |
--max-tokens | Maximum tokens to generate |
Example
reactor ai test gpt-4o --prompt "Summarize Reactor in one sentence."reactor ai test fast-chat --prompt "Hello" --system "You are a helpful assistant." --streamAuth management
Section titled “Auth management”Organization and identity management for the Reactor auth capability.
auth orgs list
Section titled “auth orgs list”reactor auth orgs listList organizations accessible to the current user.
Example
reactor auth orgs listauth orgs create
Section titled “auth orgs create”reactor auth orgs create --name <NAME> <SLUG>Create a new organization.
| Flag | Description |
|---|---|
--name | Organization display name (required) |
Example
reactor auth orgs create --name "Acme Corp" acmeauth orgs show
Section titled “auth orgs show”reactor auth orgs show <ORG_ID>Show organization details.
Example
reactor auth orgs show org_abc123auth orgs update
Section titled “auth orgs update”reactor auth orgs update <ORG_ID> [--name <NAME>] [--slug <SLUG>]Update organization name or slug.
| Flag | Description |
|---|---|
--name | New display name |
--slug | New slug |
Example
reactor auth orgs update org_abc123 --name "Acme Inc."auth orgs delete
Section titled “auth orgs delete”reactor auth orgs delete <ORG_ID>Delete an organization.
Example
reactor auth orgs delete org_abc123auth members list
Section titled “auth members list”reactor auth members list <ORG_ID>List members of an organization.
Example
reactor auth members list org_abc123auth members add
Section titled “auth members add”reactor auth members add <ORG_ID> <USER_ID> [--role <ROLE>]Add a member to an organization.
| Flag | Description |
|---|---|
--role | Member role (default: member) |
Example
reactor auth members add org_abc123 usr_xyz --role adminauth members update
Section titled “auth members update”reactor auth members update <ORG_ID> <USER_ID> <ROLE>Update a member’s role.
Example
reactor auth members update org_abc123 usr_xyz memberauth members remove
Section titled “auth members remove”reactor auth members remove <ORG_ID> <USER_ID>Remove a member from an organization.
Example
reactor auth members remove org_abc123 usr_xyzauth keys list
Section titled “auth keys list”reactor auth keys list <ORG_ID>List API keys for an organization.
Example
reactor auth keys list org_abc123auth keys create
Section titled “auth keys create”reactor auth keys create <ORG_ID> <NAME>Create a new API key.
Example
reactor auth keys create org_abc123 "CI deploy key"auth keys revoke
Section titled “auth keys revoke”reactor auth keys revoke <KEY_ID>Revoke an API key.
Example
reactor auth keys revoke key_abc123auth invitations list
Section titled “auth invitations list”reactor auth invitations list <ORG_ID>List pending invitations for an organization.
Example
reactor auth invitations list org_abc123auth invitations create
Section titled “auth invitations create”reactor auth invitations create <ORG_ID> <EMAIL> [--role <ROLE>]Invite a user by email.
| Flag | Description |
|---|---|
--role | Role for the invited user (default: member) |
Example
reactor auth invitations create org_abc123 dev@example.com --role adminauth invitations revoke
Section titled “auth invitations revoke”reactor auth invitations revoke <INVITATION_ID>Revoke a pending invitation.
Example
reactor auth invitations revoke inv_abc123Connect
Section titled “Connect”Manage connectors, webhook receivers, schema drift, and SDK codegen.
connect catalog list
Section titled “connect catalog list”reactor connect catalog listList available connector types in the catalog.
Example
reactor connect catalog listconnect catalog show
Section titled “connect catalog show”reactor connect catalog show <CONNECTOR_TYPE>Show connector type details, actions, and configuration schema.
Example
reactor connect catalog show stripereactor connect catalog show slackconnect instances list
Section titled “connect instances list”reactor connect instances listList connector instances in the project.
Example
reactor connect instances listconnect instances create
Section titled “connect instances create”reactor connect instances create <CONNECTOR_TYPE> --name <NAME> [--config <JSON|@file.json>]Create a new connector instance.
| Flag | Description |
|---|---|
--name | Instance name (required) |
--config | Configuration JSON or @file.json |
Example
reactor connect instances create stripe --name billing --config @stripe-config.jsonconnect instances show
Section titled “connect instances show”reactor connect instances show <INSTANCE_ID>Show instance details and status.
Example
reactor connect instances show inst_abc123connect instances update
Section titled “connect instances update”reactor connect instances update <INSTANCE_ID> [--name <NAME>] [--config <JSON|@file.json>]Update instance name or configuration.
| Flag | Description |
|---|---|
--name | New instance name |
--config | Updated configuration JSON or @file.json |
Example
reactor connect instances update inst_abc123 --config @updated-config.jsonconnect instances delete
Section titled “connect instances delete”reactor connect instances delete <INSTANCE_ID> [--yes]Delete a connector instance.
| Flag | Description |
|---|---|
--yes | Skip confirmation prompt |
Example
reactor connect instances delete inst_abc123 --yesconnect instances check
Section titled “connect instances check”reactor connect instances check <INSTANCE_ID>Test instance credentials and connectivity.
Example
reactor connect instances check inst_abc123connect instances credentials
Section titled “connect instances credentials”reactor connect instances credentials <INSTANCE_ID> <CREDENTIALS>Set credentials for an instance. Value may be JSON, @file.json, or - for stdin.
Example
reactor connect instances credentials inst_abc123 @creds.jsonecho '{"api_key":"sk_live_..."}' | reactor connect instances credentials inst_abc123 -connect action
Section titled “connect action”reactor connect action <INSTANCE_ID> <ACTION> [--input <JSON|@file.json|->] [--dry-run] [--idempotency-key <KEY>]Invoke an action on a connector instance.
| Flag | Description |
|---|---|
--input | Action input JSON, @file.json, or - for stdin |
--dry-run | Run in dry-run/sandbox mode |
--idempotency-key | Idempotency key for the action |
Example
reactor connect action inst_abc123 createCustomer \ --input '{"email":"user@example.com"}'reactor connect action inst_abc123 postMessage --input @message.json --dry-runconnect receivers list
Section titled “connect receivers list”reactor connect receivers listList webhook receivers.
Example
reactor connect receivers listconnect receivers create
Section titled “connect receivers create”reactor connect receivers create --name <NAME> --target-type <TYPE> --target <TARGET> [--filter <EXPR>]Create a webhook receiver.
| Flag | Description |
|---|---|
--name | Receiver name (required) |
--target-type | Target type: job, stream, action, or function (required) |
--target | Target name or connection ID (required) |
--filter | Optional filter expression |
Example
reactor connect receivers create \ --name stripe-webhooks \ --target-type job \ --target process-stripe-eventconnect receivers show
Section titled “connect receivers show”reactor connect receivers show <RECEIVER_ID>Show receiver details and endpoint URL.
Example
reactor connect receivers show rcv_abc123connect receivers delete
Section titled “connect receivers delete”reactor connect receivers delete <RECEIVER_ID> [--yes]Delete a webhook receiver.
| Flag | Description |
|---|---|
--yes | Skip confirmation prompt |
Example
reactor connect receivers delete rcv_abc123 --yesconnect receivers rotate
Section titled “connect receivers rotate”reactor connect receivers rotate <RECEIVER_ID> [--grace-seconds <SECONDS>]Rotate a receiver’s signing token.
| Flag | Description |
|---|---|
--grace-seconds | Grace period for the old token (default: 300) |
Example
reactor connect receivers rotate rcv_abc123 --grace-seconds 600connect drift list
Section titled “connect drift list”reactor connect drift list [--connection <NAME>] [--all]List schema drift events.
| Flag | Description |
|---|---|
--connection | Filter by connection name |
--all | Include all statuses, not just pending |
Example
reactor connect drift listreactor connect drift list --connection stripe-billing --allconnect drift approve
Section titled “connect drift approve”reactor connect drift approve <DRIFT_ID> [--reason <TEXT>] [--yes]Approve a pending schema drift event.
| Flag | Description |
|---|---|
--reason | Reason for approval |
--yes | Skip confirmation prompt |
Example
reactor connect drift approve drift_abc123 --reason "Field added by vendor API v2"connect drift reject
Section titled “connect drift reject”reactor connect drift reject <DRIFT_ID> [--reason <TEXT>] [--yes]Reject a pending schema drift event.
| Flag | Description |
|---|---|
--reason | Reason for rejection |
--yes | Skip confirmation prompt |
Example
reactor connect drift reject drift_abc123 --reason "Unexpected breaking change"connect codegen
Section titled “connect codegen”reactor connect codegen --instance <NAME> [--output <DIR>] [--format <FORMAT>]Generate TypeScript SDK types (or JSON Schema) for a connector instance.
| Flag | Description |
|---|---|
--instance | Instance name to generate types for (required) |
--output | Output directory (default: ./generated) |
--format | Output format: typescript or json-schema (default: typescript) |
Example
reactor connect codegen --instance billingreactor connect codegen --instance billing --output ./src/generated --format json-schemaconnect auth
Section titled “connect auth”reactor connect auth <INSTANCE_ID> [--no-browser] [--port <PORT>]Authenticate with an OAuth connector (requires connect-oauth feature).
| Flag | Description |
|---|---|
--no-browser | Print OAuth URL instead of opening a browser |
--port | Port for OAuth callback server (default: 9876) |
Example
reactor connect auth inst_abc123reactor connect auth inst_abc123 --no-browser --port 9876vault list
Section titled “vault list”reactor vault listList secret keys stored in the project vault (values are not shown).
Example
reactor vault listvault get
Section titled “vault get”reactor vault get <KEY>Retrieve a secret value.
Example
reactor vault get DATABASE_URLvault set
Section titled “vault set”reactor vault set <KEY> <VALUE>Set a secret value. VALUE may be a literal, @file.json, or - for stdin.
Example
reactor vault set API_KEY sk_live_abc123reactor vault set SERVICE_ACCOUNT @sa.jsonvault unset
Section titled “vault unset”reactor vault unset <KEY>Delete a secret from the vault.
Example
reactor vault unset OLD_API_KEYvault rotate
Section titled “vault rotate”reactor vault rotate <KEY_NAME>Rotate a transit encryption key.
Example
reactor vault rotate app-data-keyReactor.cloud control plane operations. Cloud domain commands accept --cf-token to override CF_API_TOKEN.
cloud projects create
Section titled “cloud projects create”reactor cloud projects create <NAME> [--region <REGION>] [--subdomain <LABEL>] [--cf-token <TOKEN>]Create a new cloud project.
| Flag | Description |
|---|---|
--region | Deployment region |
--subdomain | Provision a *.reactor.cloud subdomain (label or FQDN) |
--cf-token | Cloudflare API token (overrides CF_API_TOKEN) |
Example
reactor cloud projects create my-app --region us-east --subdomain my-appcloud projects list
Section titled “cloud projects list”reactor cloud projects list [--owner <UUID>] [--limit <N>] [--offset <N>]List cloud projects.
| Flag | Description |
|---|---|
--owner | Filter by owner user ID |
--limit | Maximum results (default: 50) |
--offset | Pagination offset (default: 0) |
Example
reactor cloud projects list --limit 20cloud projects show
Section titled “cloud projects show”reactor cloud projects show <PROJECT_REF>Show project details.
Example
reactor cloud projects show prj_abc123cloud projects delete
Section titled “cloud projects delete”reactor cloud projects delete <PROJECT_REF> [--yes]Delete a cloud project.
| Flag | Description |
|---|---|
--yes | Skip confirmation prompt |
Example
reactor cloud projects delete prj_abc123 --yescloud keys list
Section titled “cloud keys list”reactor cloud keys list <PROJECT_REF>List API keys for a cloud project.
Example
reactor cloud keys list prj_abc123cloud keys create
Section titled “cloud keys create”reactor cloud keys create <PROJECT_REF> --kind <KIND>Create a new API key.
| Flag | Description |
|---|---|
--kind | Key kind: anon or service (required) |
Example
reactor cloud keys create prj_abc123 --kind servicecloud keys rotate
Section titled “cloud keys rotate”reactor cloud keys rotate <PROJECT_REF> <KEY_ID>Rotate an API key.
Example
reactor cloud keys rotate prj_abc123 key_abc123cloud keys revoke
Section titled “cloud keys revoke”reactor cloud keys revoke <PROJECT_REF> <KEY_ID>Revoke an API key.
Example
reactor cloud keys revoke prj_abc123 key_abc123cloud members list
Section titled “cloud members list”reactor cloud members list <PROJECT_REF>List members of a cloud project.
Example
reactor cloud members list prj_abc123cloud members add
Section titled “cloud members add”reactor cloud members add <PROJECT_REF> <USER_ID> [--role <ROLE>]Add a member to a cloud project.
| Flag | Description |
|---|---|
--role | Member role: admin or member (default: member) |
Example
reactor cloud members add prj_abc123 usr_xyz --role admincloud members remove
Section titled “cloud members remove”reactor cloud members remove <PROJECT_REF> <USER_ID>Remove a member from a cloud project.
Example
reactor cloud members remove prj_abc123 usr_xyzcloud domains add
Section titled “cloud domains add”reactor cloud domains add <NAME> [--target <HOSTNAME>] [--cf-token <TOKEN>]Add a subdomain to reactor.cloud (creates Cloudflare CNAME).
| Flag | Description |
|---|---|
--target | CNAME target hostname (default: rc-shared-1-edge.fly.dev) |
--cf-token | Cloudflare API token (overrides CF_API_TOKEN) |
Example
reactor cloud domains add my-appreactor cloud domains add my-app.reactor.cloud --target rc-shared-1-edge.fly.devcloud domains list
Section titled “cloud domains list”reactor cloud domains list [--cf-token <TOKEN>]List reactor.cloud subdomains.
| Flag | Description |
|---|---|
--cf-token | Cloudflare API token (overrides CF_API_TOKEN) |
Example
reactor cloud domains listcloud domains remove
Section titled “cloud domains remove”reactor cloud domains remove <NAME> [--yes] [--cf-token <TOKEN>]Remove a subdomain from reactor.cloud.
| Flag | Description |
|---|---|
--yes | Skip confirmation prompt |
--cf-token | Cloudflare API token (overrides CF_API_TOKEN) |
Example
reactor cloud domains remove my-app --yescloud audit
Section titled “cloud audit”reactor cloud audit <PROJECT_REF> [--limit <N>]View the audit log for a cloud project.
| Flag | Description |
|---|---|
--limit | Maximum entries to show (default: 50) |
Example
reactor cloud audit prj_abc123 --limit 100Local development server commands. Require the dev feature in the CLI build.
reactor dev [--host <HOST>] [--port <PORT>] [--db <URL>] [--ephemeral] [--admin-token <TOKEN>] [--context <NAME>]Start a foreground local Reactor server.
| Flag | Description |
|---|---|
--host | Host to bind to (default: 127.0.0.1) |
--port | Port to listen on (default: 8080) |
--db | Database URL (conflicts with --ephemeral) |
--ephemeral | Use docker-managed ephemeral Postgres |
--admin-token | Admin token for the server |
--context | Context name for the local server |
Example
reactor devreactor dev --ephemeral --port 9090reactor dev --db postgres://localhost:5432/reactor_devreactor up [--host <HOST>] [--port <PORT>] [--db <URL>] [--ephemeral] [--admin-token <TOKEN>] [--context <NAME>] [--force]Start a detached local Reactor server in the background.
| Flag | Description |
|---|---|
--host | Host to bind to (default: 127.0.0.1) |
--port | Port to listen on (default: 8080) |
--db | Database URL (conflicts with --ephemeral) |
--ephemeral | Use docker-managed ephemeral Postgres |
--admin-token | Admin token for the server |
--context | Context name for the local server |
--force | Force restart if already running |
Example
reactor up --ephemeralreactor up --context local-dev --forcereactor down [--context <NAME>]Stop a detached local server.
| Flag | Description |
|---|---|
--context | Context for the detached server |
Example
reactor downreactor down --context local-devstatus
Section titled “status”reactor status [--context <NAME>] [--all]Show status of local development servers.
| Flag | Description |
|---|---|
--context | Context for a specific detached server |
--all | Show status of all servers |
Example
reactor statusreactor status --allreactor status --context local-devUtility
Section titled “Utility”inspect
Section titled “inspect”reactor inspect <KIND> <NAME>Inspect a resource by kind and name or ID.
Supported kinds: function, site, job, org, member, key, bucket, domain.
Example
reactor inspect function send-emailreactor inspect site webreactor inspect org org_abc123reactor logs <CAPABILITY> [<NAME>] [--since <DURATION>] [-f|--follow]View logs across capabilities.
| Argument / Flag | Description |
|---|---|
CAPABILITY | Capability name: functions, sites, or jobs |
NAME | Optional resource name |
--since | Show logs since a duration |
-f, --follow | Follow logs via polling |
Example
reactor logs functions send-email --since 1hreactor logs sites webreactor logs jobs -ftypes generate
Section titled “types generate”reactor types generate [-o|--output <PATH>]Generate TypeScript types from the database schema.
| Flag | Description |
|---|---|
-o, --output | Output file path (default: ./database.types.ts) |
Example
reactor types generatereactor types generate --output ./src/database.types.ts