Repository navigation
fix: expose CoreWeave API key setup in apps - #7
Merged
Merged
Conversation
JustinPerlman
approved these changes
Oct 8, 2026
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.
CoreWeave is missing from OpenClaw’s pasted API key provider list because its manifest does not advertise app-guided secret setup. Declare
appGuidedSecret: true; the existing auth helper already accepts a supplied key and selects the default model without requiring a project.Validated with
npm run typecheck,npm test(17 passing), andnpm run build. This enables the installed plugin’s key-entry option. Fresh-install discoverability also needs the catalog/setup changes in openclaw/openclaw#166965 and a published plugin version containing this manifest change.