Repository navigation
fix(models): report honest provider credential status - #6538
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
3 Skipped Deployments
|
GitHub Actions
Error
![diff-warden[bot]](https://avatars.githubusercontent.com/u/118544361?s=60&v=4){kind=small}
There was a problem hiding this comment.
Warden clearance. Complete security and confidentiality review of c0c3947e62d2db3c98cd80ef3fff7e27cad12309 found no high or medium security findings and no confidentiality findings. Any new push dismisses this approval. Analysis run
Warden: approvedNo high or medium security findings and no confidentiality findings. Reviewed |
GitHub Actions
Error
There was a problem hiding this comment.
Warden clearance. Complete security and confidentiality review of c056af3a3db68133c5cca1056d39128353bd2512 found no high or medium security findings and no confidentiality findings. Any new push dismisses this approval. Analysis run
GitHub Actions
Error
There was a problem hiding this comment.
Warden clearance. Complete security and confidentiality review of a866ddc4f12627c52903e54edbf92a101b49e63a found no high or medium security findings and no confidentiality findings. Any new push dismisses this approval. Analysis run
GitHub Actions
Error
There was a problem hiding this comment.
Warden clearance. Complete security and confidentiality review of a10c8e3c3aecd2e6b039b068554ad62cdbe57003 found no high or medium security findings and no confidentiality findings. Any new push dismisses this approval. Analysis run
GitHub Actions
Error
There was a problem hiding this comment.
Warden clearance. Complete security and confidentiality review of b7ef89e1e70061cddf3ce2dd9e5462ba1b6a4f38 found no high or medium security findings and no confidentiality findings. Any new push dismisses this approval. Analysis run
There was a problem hiding this comment.
Warden clearance. Complete security and confidentiality review of dee4d32ab46ccd2695c59b2227daac12089d4e72 found no high or medium security findings and no confidentiality findings. Any new push dismisses this approval. Analysis run
What is this about?
AI Providers distinguishes saved, verified and rejected credentials instead of treating a saved key as proof it works.
What problem does it solve?
A provider can reject a chat with an authentication error while Settings still claims it is ready.
What was the situation before?
Saving an invalid key listed models and showed “Ready to use,” even after a chat returned 401.
How is this implemented?
providerCredentialStatus(cloud and self-hosted, off). Turning it off restores the previous status UI without changing credentials or chats. Rollout docs.What else changed?
none
Release note
AI Providers can distinguish an untested or rejected key from a provider that has successfully answered a chat.
Evidence
evals/proofs/provider-credential-status.proof.test.ts— before: saved and rejected keys claimed readiness; after: saved keys are unchecked, a loopback-provider 401 shows Key not accepted, replacement clears it, and success earns Ready to use.Design: P1, P5, C6, V2