Skip to main content
Sparkles exposes the models accepted by the active local harness. It does not grant model access or bypass the harness provider’s authentication, account entitlements, rollout rules, or installed version.

​
Why a model may be unavailable

The /model list depends on four things:
  1. The selected harness is installed and available on PATH.
  2. You are authenticated with that harness or its configured provider.
  3. Your provider account can use the model.
  4. The installed harness reports or accepts that model identifier.
Sparkles combines its built-in catalog with the effective current model reported by Claude Code, Codex, or OpenCode. A custom configured model can therefore appear even when it is not in the built-in list. Run sparkles doctor to inspect the installed runtimes, then use /agent before /model when you need to switch providers.

​
Use Fable

With Claude Code installed and authenticated:
Inside the TUI, the same setup is:
  1. Run /agent and choose claude.
  2. Run /model and choose Fable 5.
  3. Run /effort and choose Ultracode.
With an OpenCode provider that exposes Anthropic models:
OpenCode’s Anthropic profile supports up to max; the Claude harness exposes the separate ultracode level for supported models.

​
Built-in model catalog

The current catalog includes the following defaults. Installed-runtime discovery can add or preserve other configured models.

​
Claude Code

Quote model values that contain square brackets so the shell does not expand them as a pathname pattern:

​
Codex

​
OpenCode

​
Reasoning effort values

Effort is model-specific. The TUI shows friendly labels while configuration and flags use the values below. The selector only offers values supported by the active model: Use CLI configuration to make a harness, model, and effort the default for a repository.