Repository navigation
fix(diagnostics): fail the credentials check when keys don't match th… - #245
Closed
MartinYuNilsen wants to merge 1 commit into
Closed
MartinYuNilsen wants to merge 1 commit into
MartinYuNilsen wants to merge 1 commit into
Conversation
…e config The credentials probe passed whenever any provider key existed. With only an Anthropic key and config/artemis.jsonc naming Google models, mobile_diagnose reported "Active (Claude)" and then every task died within seconds with "Planner requires GOOGLE_API_KEY". The probe now also runs the loaded LLM config's validate_providers() and, when keys exist but a configured agent node lacks its provider's key, fails with "Key Does Not Match Config", the offending node, the keys that are configured, and how to align them. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…e config
The credentials probe passed whenever any provider key existed. With only an Anthropic key and config/artemis.jsonc naming Google models, mobile_diagnose reported "Active (Claude)" and then every task died within seconds with "Planner requires GOOGLE_API_KEY".
The probe now also runs the loaded LLM config's validate_providers() and, when keys exist but a configured agent node lacks its provider's key, fails with "Key Does Not Match Config", the offending node, the keys that are configured, and how to align them.