CLI reference¶

All commands are available via rp (or repster). Cloud commands walk you through login/registration inline if you haven't authenticated yet; you never need to run rp login before your first rp deploy.

Local commands¶

Command	Description
`rp dev`	Start the local scheduler; fires cron-scheduled flows according to their `@rp.flow(schedule=...)` expressions
`rp run <flow>`	Run a flow now (local execution)
`rp list`	List all discovered flows with their schedule and next run time
`rp status [<flow>] [--profile]`	Show last N runs and next scheduled run; merges local and cloud runs when a profile is configured
`rp logs [--flow <name>] [--run <id>] [--profile]`	View captured log output for a run
`rp retry [--flow <name>] [--run <id>] [--profile]`	Re-run a flow, linked to the run it retries

Schedules are declared in @rp.flow(schedule=...) in code, not set via the CLI.

Cloud commands¶

Command	Description
`rp login [--token rpk_...] [--profile NAME]`	Authenticate with Repster Cloud; interactive email-first flow: logs in if you have an account, registers if you don't. Writes a profile to `~/.repster/config.toml`. Pass `--token rpk_...` to skip interactive flow (for CI).
`rp deploy [--profile NAME]`	Package the project and push to the control plane; immutable and content-addressed; deploying the same code twice is a no-op
`rp run --cloud <flow> [--profile NAME]`	Trigger a cloud run of the latest deployment; fails with a helpful message if no deployment exists
`rp cancel <run-id> [--yes] [--profile NAME]`	Cancel (kill) an in-flight cloud run; admin only; `--yes` skips confirmation
`rp usage [--profile NAME]`	Show this org's run count, compute, and estimated spend for the current month (vs the monthly cost cap)
`rp secrets push [--profile NAME]`	Read `.env` and store its values in the cloud secrets vault
`rp secrets list [--profile NAME]`	List secret key names stored in the vault for this project (values are never returned)
`rp secrets delete KEY [--yes] [--profile NAME]`	Delete a secret from the vault for this project; prompts for confirmation unless `--yes`

Org management¶

Command	Description
`rp org list [--profile]`	List all orgs you belong to (slug, name, role, joined date)
`rp org switch <slug>`	Set the default profile to a different org
`rp org invite <email> [--role member\\|admin] [--profile]`	Invite a user; creates an account with a temporary password if needed
`rp org members [--profile]`	List members (email, role, joined date)
`rp org members promote <email> [--profile]`	Promote a member to admin
`rp org members remove <email> [--yes] [--profile]`	Remove a member; `--yes` skips confirmation

Key management¶

Command	Description
`rp keys list [--profile]`	List API keys for this org (prefix, name, status, last-used, created)
`rp keys create [--name NAME] [--profile]`	Create a new API key; raw key is printed once
`rp keys revoke <key-id-or-prefix> [--yes] [--profile]`	Revoke a key; `--yes` skips confirmation

Global flags¶

All commands that talk to the cloud accept:

Flag	Description
`--profile NAME`	Use a named profile from `~/.repster/config.toml`

rp login additionally accepts --service-url URL to point at a specific Repster Cloud host (persisted into the profile).

Environment variables REPSTER_SERVICE_URL and REPSTER_API_TOKEN are also accepted and override the profile.

See Configuration for the full resolution chain.