troubleshooting
Fix provider authentication errors
Authentication errors usually come from missing credentials, expired subscriptions, unsupported model IDs, or incorrect precedence. Check ~/.prime/agent/auth.json mode 0600, verify the provider is enabled in your subscription or models.json, and confirm the selected model supports the requested capability. Redact keys before sharing logs.
First-party announcement, documentation, release, or installer.
Symptom
Symptom
The agent cannot log in, the model list is empty, or the selected model refuses to stream.
Diagnosis
Credentials, permissions, and model availability are the likely causes.
Safe fix
Re-authenticate, confirm auth.json permissions, and switch to a supported provider/model pair.
Verification
Run a short prompt and verify that the model selection screen shows the expected provider.
Rollback
Restore the previous provider choice or credentials if the new pair is worse.
Diagnosis
Symptom
The agent cannot log in, the model list is empty, or the selected model refuses to stream.
Diagnosis
Credentials, permissions, and model availability are the likely causes.
Safe fix
Re-authenticate, confirm auth.json permissions, and switch to a supported provider/model pair.
Verification
Run a short prompt and verify that the model selection screen shows the expected provider.
Rollback
Restore the previous provider choice or credentials if the new pair is worse.
Safe fix
Symptom
The agent cannot log in, the model list is empty, or the selected model refuses to stream.
Diagnosis
Credentials, permissions, and model availability are the likely causes.
Safe fix
Re-authenticate, confirm auth.json permissions, and switch to a supported provider/model pair.
Verification
Run a short prompt and verify that the model selection screen shows the expected provider.
Rollback
Restore the previous provider choice or credentials if the new pair is worse.
Verification
Symptom
The agent cannot log in, the model list is empty, or the selected model refuses to stream.
Diagnosis
Credentials, permissions, and model availability are the likely causes.
Safe fix
Re-authenticate, confirm auth.json permissions, and switch to a supported provider/model pair.
Verification
Run a short prompt and verify that the model selection screen shows the expected provider.
Rollback
Restore the previous provider choice or credentials if the new pair is worse.
Rollback
Symptom
The agent cannot log in, the model list is empty, or the selected model refuses to stream.
Diagnosis
Credentials, permissions, and model availability are the likely causes.
Safe fix
Re-authenticate, confirm auth.json permissions, and switch to a supported provider/model pair.
Verification
Run a short prompt and verify that the model selection screen shows the expected provider.
Rollback
Restore the previous provider choice or credentials if the new pair is worse.