Ignore unusable LLM keys for workflow bootstrap#398
Merged
Conversation
Contributor
|
Reviews (1): Last reviewed commit: "Ignore unusable LLM keys for workflow bo..." | Re-trigger Greptile |
Contributor
|
Reviews (2): Last reviewed commit: "Keep fallback LLM key and model aligned" | Re-trigger Greptile |
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
1 participant
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.
Summary
Root cause
Cron workflow claws can be created with empty default_model and llm_key when the workspace/workflow does not specify them. If the hub has a stale blank OpenAI key, bootstrap still selected/exported it, leaving OpenClaw to ask for OpenAI auth even though the workflow never requested OpenAI.
Tests