bullpen login

Last updated: May 29, 2026

Log in to Bullpen via device auth (RFC 8628): displays a code, opens browser

Usage

bullpen login [OPTIONS]

Live Help

Log in to Bullpen via device auth (RFC 8628): displays a code, opens browser

Usage: bullpen login [OPTIONS]

Options:
      --non-interactive


      --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
          Suppress the split-brain warning even when assets are detected on non-selected wallets

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

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

EXAMPLES:
  bullpen login --help
      Show options for this command without signing, submitting, or changing state.

Example Commands

bullpen login [OPTIONS]
bullpen login --help
bullpen login --output json

JSON Output

Contract: JSON Output Contract.

This command supports --output json, but this generated reference page intentionally does not include a synthetic success schema or example.

Use the live command in your target environment to inspect command-specific success fields. Error output follows the shared JSON output contract linked above.

Schema version: 1 when a command emits schema_version; otherwise treat the current command shape as contract version 1.

Stability

Patch releases may add nullable or optional fields. Minor releases may add required fields or increment schema_version. Major releases may remove or rename fields.