Date: 2026-09-14

​
Model configuration

Nova selects models through provider authentication, registered model configuration, runtime routing, availability, quotas, and organisation policy. A model name alone does not make a model usable.

​
Configure authentication first

Use the setup flow to configure access:
The current CLI also supports --compass-key and --anthropic-key for non-interactive setup, but command-line values can be recorded in shell history. Prefer the setup flow or a secure automation environment.

​
Manage registered models

Use the models command to inspect the management options provided by your installation:
Custom registrations are subject to the provider, credentials, policy, and model availability checks in the running session.

​
Diagnose an unavailable model

Check these in order:
  1. Authentication is configured and valid.
  2. The provider and model are enabled by your organisation and current policy.
  3. The account has the required quota and service access.
  4. The model name and registration match the installed Nova version.
Use nova setup --validate-key for a read-only credential check, then use the relevant command help or diagnostic output. Do not include secrets in tickets, logs, or screenshots.

​
Boundaries

Provider outages, quota changes, organisation controls, and runtime policy can make a previously configured model unavailable. Keep fallbacks and production automation explicit rather than assuming a silent substitution.