Configuration

Sume CLI reads configuration from environment variables first, then from the local config file.

Configuration precedence

Environment variables.
Local config in SUME_CONFIG_DIR or ~/.sume/config.json.
Built-in defaults.

The default Public API base is:

Environment variables

Variable	Use
`SUME_API_KEY`	API key for Public API calls. Preferred for CI and secret managers.
`SUME_API_BASE_URL`	Optional API base URL override. Defaults to `https://www.sume.so/api/v1`.
`SUME_CONFIG_DIR`	Optional directory for local CLI config. Useful for sandboxes and tests.
`SUME_NO_UPDATE`	Set to `1` to disable background binary update checks.
`SUME_SKILLS_URL`	Optional skills registry override. Defaults to `https://cli.sume.so/skills/registry`.
`SUME_SKILLS_API_URL`	Optional skills search API override. Defaults to `https://cli.sume.so/skills`.

Example:

Local setup

Store local defaults:

Configure update behavior:

Inspect auth and context:

JSON output

Use the global --json flag whenever another process will parse the result:

JSON errors are also structured when --json is present. Agents should prefer JSON for command execution and keep human output for local debugging.

API base overrides

Most users should keep the default production Public API base. Override SUME_API_BASE_URL only when you are intentionally testing another public API environment:

Do not point the CLI at internal app, database, Railway, or provider URLs. The CLI is a Public API client.

Disposable sandboxes

For Modal, CI, or temporary agent sandboxes:

Clean up when finished:

Do not bake personal API keys into reusable sandbox snapshots.