1. --stage

   flag (per-command override)

2. ~/.owlpay-wallet-pro/config.json

   (persistent)
3. Default (

   prod

   )

RESULT=$(owlp env get --json 2>/dev/null) && echo "$RESULT" | jq '.data | {env, source}'   # Show current env
owlp env set stage               # Persist env to config.json
owlp env set prod                # Switch back to prod
RESULT=$(owlp balance --stage --json 2>/dev/null) && echo "$RESULT" | jq -r '.data[] | "\(.symbol): \(.balance)"'   # One-off stage override

stage

env

--json

{"type":"meta.env",...}

• --json

  — machine-readable output (always use when parsing programmatically)

• --stage

  — use stage environment instead of the persisted / default env

• --wallet <name>

  — use a specific wallet instead of the default

• --debug

  — verbose logging to stderr

• skills/commands/env.md

  — Environment management (get/set, config.json)

• skills/commands/auth.md

  —

  auth login

  /

  auth logout

  /

  auth status

• skills/commands/onboard.md

  — Guided setup (account + wallet + KYC)

• skills/commands/wallet.md

  — Wallet create, import/restore, list, rename, switch, export-key, reset

• skills/commands/balance.md

  — Balance queries across chains and tokens

• skills/commands/tx.md

  — Transaction history, filters, pagination, and detail

• skills/commands/send.md

  — Send tokens (preview + submit), NDJSON event stream

• skills/commands/chains.md

  — Supported chains and tokens

• skills/commands/verify.md

  — Address verification and chain auto-detection

• skills/commands/countries.md

  — Countries allowed for individual registration

• skills/commands/kyc.md

  — KYC status check and browser-assisted submission

• skills/commands/status.md

  — Unified readiness dashboard (account, KYC, wallets)

• skills/commands/reset.md

  —

  owlp reset

  (active env) /

  owlp reset --all

  (everything)

Reminder: every

owlp ... --json

call below must follow § Output Discipline — capture to a variable, parse with jq, never expose raw JSON.

1. Natural language first. Summarize results conversationally, as if reporting to a colleague. Do not paste raw JSON output. Use lists or tables only when data volume makes prose hard to scan — the choice is yours.
2. Event streams: report the outcome, not the journey. For commands that emit NDJSON event streams (

   send

   ,

   onboard

   ,

   kyc submit

   ), wait for the final result and summarize it once. Do not narrate each intermediate event.
3. Errors: include the code and a next step. When a command fails, mention the error code (e.g.

   INSUFFICIENT_GAS

   ) and suggest what the user can do about it. Each command's documentation describes its common errors.
4. Sensitive operations: warn before executing. Before running

   wallet create

   ,

   wallet import

   , or

   wallet export-key

   , explain the risks (mnemonic loss, private key exposure) and ask the user to confirm. Do not execute the command first and warn after.
5. Respect the command's

   ## Agent Response

   section. Individual command docs may include an

   ## Agent Response

   section with specific guidance on what to highlight and how to present results. Follow those instructions; they override these general principles where they differ.

~/.owlpay-wallet-pro/

• config.json

  — persisted env (

  {"env":"prod"|"stage"}

  ), root level, shared across envs

• prod/auth.json

  ,

  stage/auth.json

  — session tokens + workspace (env-scoped)

• prod/wallets.json

  ,

  stage/wallets.json

  — addresses + mnemonics (env-scoped)