bullpen login

Last updated: July 13, 2026

Log in to Bullpen in your browser

Usage

bullpen login [OPTIONS]

Live Help

Log in to Bullpen in your browser

Usage: bullpen login [OPTIONS]

Options:
      --non-interactive
          Refuse browser/device login; use an existing logged-in BULLPEN_HOME for automation

      --output <OUTPUT>
          Output format for command results

          [possible values: table, json]

      --env <ENV>
          Target environment to connect to (overrides config.toml)

          [env: BULLPEN_ENV=]
          [possible values: staging, production]

      --webapp-url <WEBAPP_URL>
          Override the web app URL for browser login (e.g., http://dev-hongjun-app.bullpen.fi)

      --config <CONFIG>
          Path to a custom config.toml file (overrides $BULLPEN_CONFIG and the default location).

          Explicit --config and BULLPEN_CONFIG paths fail closed: if the file is missing, the CLI exits validation instead of silently loading defaults. Credentials still resolve via BULLPEN_HOME, so set BULLPEN_HOME too when isolating a session.

      --skip-init
          Skip post-login wallet initialization

      --no-browser
          Skip opening the browser and QR code — just print the verification URL and code

      --no-split-brain-warning
          Compatibility flag retained for scripts. Passive status does not probe split-brain wallet state

      --read-only
          Enable read-only mode: blocks all mutating commands

  -h, --help
          Print help (see a summary with '-h')

NEXT:
  After login completes, run `bullpen status`.
  If status says action is needed, run `bullpen fix --refresh`.

RECOVERY:
  If browser launch fails, run `bullpen login --no-browser`.
  If local auth cannot be read, run `bullpen fix --refresh`.
  If support review is needed, run `bullpen support` and attach the generated artifact.

EXAMPLES:
  # Show login options without starting device auth
  bullpen login --help

Example Commands

bullpen login --help