Configuration

cn resolves its configuration (models, MCP servers, rules, etc.) from several sources, in this order:
  1. --config flag — a file path passed at launch
  2. Saved config — the last-used configuration, persisted across sessions
  3. Default — ~/.continue/config.yaml

--config flag

Point cn at a local YAML file:
cn --config ./my-config.yaml
This overrides any saved preference for the current session.

Switching at runtime

Use /config inside a TUI session to switch between available configurations:
> /config
This shows your available local configs. The selection is saved for next time.

config.yaml

cn looks for ~/.continue/config.yaml. This file uses the same format as the IDE extensions — see config.yaml reference for the full schema.

CLI-specific flags

Several flags inject configuration at launch without editing a file:
# Add rules (file path or inline string)
cn --rule ./rules/style.md
cn --rule "Always use TypeScript strict mode"

# Load an agent file
cn --agent my-org/pr-reviewer
All of these are repeatable — pass them multiple times to add multiple items.

Secrets

Store sensitive values (API keys, tokens) as environment variables. Reference them in config with:
${{ secrets.MY_API_KEY }}
Headless ModeTool Permissions