Provider and model issues
Recover from missing keys, inactive providers, empty catalogs, refresh errors, and unsupported model capabilities.
On this page
No providers appear in the composer
Likely cause: no provider is configured.
- Open Settings → Providers.
- Save the required key, or confirm a keyless local Ollama/private Custom host.
- Set Active provider. Saving a key alone does not switch it.
- Return to chat and reopen the model picker.
Expected empty-state text is No providers configured — open Settings → Providers.
Active provider is empty
The Active menu lists configured hosts only. If it says No providers configured yet. Add an API key below or use local Ollama, confirm secure storage accepted the key. For Ollama, confirm whether the host is local or Ollama Cloud; Cloud requires a key.
Refresh models fails
Check in this order:
- Provider key status.
- Ollama base URL or Custom OpenAI base URL.
- Network reachability to the configured host.
- Provider response or rate-limit text.
- Retry
Refresh modelsonce.
Seed model names can remain visible when the live catalog fails. They are fallback metadata, not proof that chat will succeed.
Some Custom hosts serve chat but no model list (HTTP 405 or 501 on GET /models — e.g. Cloudflare Workers AI compat). The catalog then shows a “does not serve a model list” notice instead of an error: the host is reachable and chat connects. Type the model ID in the composer model picker search and press Enter to use it manually; a wrong ID surfaces as the host’s own HTTP error during the run. HTTP 404 usually means the base URL is wrong — fix it in Settings, then refresh.
A model cannot use an attachment or control
The selected model metadata may not advertise image, native file, audio, tools, thinking, structured output, or a service tier. Choose a model with the required capability. Do not force a provider-specific parameter by changing unrelated settings.
Secure storage reports a failure
Agent V refuses plaintext fallback for provider and MCP secrets. Fix operating-system keychain or secure-storage availability, then save again. Do not place the key in a rule, skill, prompt, or workspace file.
If a provider request still fails, preserve provider ID, model ID, base URL host without credentials, exact error, and app version.