Global Flags

Every rensei command inherits a set of persistent flags from the root command. These flags override the corresponding values in ~/.config/rensei/config.json and the environment variables for a single invocation without touching your saved configuration.

Flag reference

Precedence

When a setting can come from multiple sources, the CLI resolves it in this order:

--flag (per-invocation)
  > RENSEI_* environment variable
    > ~/.config/rensei/config.json (active context / saved settings)
      > compiled-in default

For example, if RENSEI_API_URL=https://staging.rensei.ai is set in your shell and you pass --url https://app.rensei.ai, the flag wins.

Examples

Run a command against a different org

rensei --org other-corp org show

Use a service account context for a single command

rensei --auth ci-deploy fleet list

Pass a token without storing it

printf '%s' "$EPHEMERAL_TOKEN" | rensei --token-stdin fleet list

Non-interactive script with JSON output

rensei --no-interactive --json --org acme-corp capacity show \
  | jq '.pools[] | select(.mode == "persistent")'

Override the platform URL (staging environment)

rensei --url https://staging.app.rensei.ai --org acme-corp status

Using global flags in shell functions

A common pattern for scripts that need to operate across multiple orgs:

#!/usr/bin/env bash
rensei_for_org() {
  local org="$1"
  shift
  rensei --auth "ci-${org}" --org "${org}" --no-interactive --json "$@"
}

rensei_for_org acme-corp fleet list
rensei_for_org other-corp fleet list

Related

• Auth - managing named auth contexts referenced by --auth
• Config - persistent defaults written by rensei config set and rensei setup
• Environment variables - env-var equivalents for most global flags