Oore CI
ReferenceCLI

`oore config`

Read and write persistent daemon URL and session-token defaults for the Oore CLI.

oore config stores defaults used by other CLI commands.

oore config set <KEY> <VALUE>
oore config get <KEY>

Keys

KeyMeaning
daemon_urlBackend base URL
session_tokenStored session fallback used by oore status

Other keys are rejected.

oore config set daemon_url https://ci.example.com
oore config get daemon_url

The default file is <install-root>/config.json, normally ~/.oore/config.json. Set OORE_CONFIG_FILE to use another path. On Unix, Oore writes the file with mode 0600 because it can contain a session token.

Resolution order

Commands that use the stored daemon default resolve a URL in this order:

  1. The command’s --daemon-url option
  2. OORE_DAEMON_URL
  3. daemon_url in the CLI config
  4. http://127.0.0.1:8787

oore status resolves a token in this order:

  1. The command’s --token option
  2. OORE_SESSION_TOKEN
  3. session_token in the CLI config

Oore uses the stored token only when the selected URL matches the stored daemon_url.

Changing daemon_url to another endpoint clears the stored token. This prevents Oore from sending one backend’s token to another backend.

oore login writes both values after validating or creating a session. Some commands define their own URL or token requirement instead of using these stored defaults; their --help output is authoritative.

`oore uninstall`

Remove owned Oore components while preserving data, or explicitly purge canonical Oore data.

`oore recovery`

Mint a short-lived, single-use browser recovery link from the backend host.

On this page

KeysResolution order