Where the CLI stores profiles, how env vars override them, and how to keep CI deterministic.

Config file (planned)

Default path:

~/.config/tradeics/config.toml          # macOS / Linux
%AppData%\tradeics\config.toml          # Windows

Override with TRADEICS_CONFIG or --config <path>.

Example:

[default]
base_url = "https://api.tradeics.example/v2"
llm_base_url = "https://llm.tradeics.example/v1"
format = "table"

[profiles.staging]
api_key = "trd_test_..."
base_url = "https://api.tradeics.example/v2"

[profiles.prod]
api_key = "trd_live_..."

Environment variables

Variable	Purpose
TRADEICS_API_KEY	REST / MCP bearer token
TRADEICS_LLM_API_KEY	LLM proxy key
TRADEICS_PROFILE	Default profile name
TRADEICS_BASE_URL	REST base override
TRADEICS_LLM_BASE_URL	LLM base override
TRADEICS_CONFIG	Config file path
NO_COLOR	Disable color when set

CI recommendations

1. Pass secrets via the CI secret store into TRADEICS_API_KEY — do not bake profiles into images.
2. Run tradeics doctor as a job preface.
3. Prefer --format json and stable paths for assertions.
4. Pin CLI version (tradeics@version) in release pipelines.
5. Use separate staging keys; never point sandbox jobs at production profiles.

Telemetry / updates (planned)

• Opt-in version check: tradeics update check
• Upgrade in place when package managers allow (brew upgrade tradeics, npm update -g @tradeics/cli)

Next

• CommandsFull command map.Read
• InstallGet the binary.Read
• Versioning & environmentsStaging vs prod.Read