Coding provider unavailable or signed out
Identify whether a provider problem comes from installation, authentication, or the selected model.
Last updated 16 September 2026
Identify whether a provider problem comes from installation, authentication, or the selected model.
Before you start
Read the exact error in the failed conversation and note which provider it used. New agents, Quick Ask, and quick generation can use different defaults.
Check the default for the feature that failed. New agents, Quick Ask, and quick generation can point to different providers or models.
Step by step
Check the provider and model in the affected composer. Confirm you are troubleshooting the provider that actually failed.
If the provider is not installed or asks for sign-in, complete its supported local setup or sign-in flow. Changing a model does not create account access.
Open Settings → AI generation and check the default for the affected feature. Compare it with the override shown in the current conversation.
Try a small read-only question after completing setup. Confirm that a real response arrives before restarting a large task.
If the error names a missing model, tool, or permission, address that specific cause. Full access does not supply credentials or an unavailable model.
If it still fails, record the provider, model, exact error, and time for a support report. Remove tokens and private request content before sharing.
What to expect
You can retry with a working provider configuration or report a specific unresolved failure.
Troubleshooting and useful details
A successful request through one provider does not prove another provider is authenticated. Repeated retries with unchanged credentials usually repeat the same failure. Follow your provider’s current setup guidance for installation and login.