Skip to content

Setup Commands

Quick-start: write a minimal .env with MAGE credentials so a fresh checkout can run care straight away. Prompts interactively for any value you don’t pass; --non-interactive falls back to documented defaults for unattended runs.

Terminal window
care init # interactive prompts
care init --non-interactive \
--api-key sk-or-v1-... \
--base-url https://openrouter.ai/api/v1 \
--model qwen/qwen3-coder \
--mode interactive
FlagDefaultPurpose
--env-path./.envWhere to write the .env.
--api-keypromptMAGE API key.
--base-urlprompt (https://openrouter.ai/api/v1)OpenAI-compatible base URL.
--modelprompt (qwen/qwen3-coder)Model id the endpoint understands — qwen/qwen3-coder is the recommended OpenRouter convention.
--mode interactive|production|ad_hocprompt (interactive)Chat default mode.
--forceoffOverwrite the target file if it exists.
--non-interactiveoffDon’t prompt — unset values use defaults (required for CI).

Diagnostic report: which env vars are set, the config path, installed extras, and deep network probes against Memory / MAGE / Platform.

Terminal window
care doctor
care doctor --no-probes # env / config / extras only (offline / CI)
care doctor --config ./care.toml # check a specific config file
FlagPurpose
--config PATHOverride the config path (default ~/.config/care/config.toml).
--no-probesSkip the network probes.

Move literal *_api_key values in ~/.config/care/config.toml into the system keystore and rewrite the TOML with keystore://… URLs.

Terminal window
care migrate-secrets --dry-run # preview without changing anything
care migrate-secrets
FlagPurpose
--config PATHOverride the config path.
--dry-runPrint what would migrate without touching the keystore or TOML.