fix: detect 'everclaw/' provider misconfiguration during install (v0.9.6)#12
Merged
DavidAJohnston merged 1 commit intomainfrom Feb 15, 2026
Merged
Conversation
…9.6) Adds post-bootstrap config validation that catches the #1 onboarding issue: using 'everclaw/' as a model prefix. Everclaw is a skill, not a provider — this silently routes to Venice instead of Morpheus. Triggered by real user report (Alex) who staked MOR correctly but got billing errors because requests never reached the Morpheus network.
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
2 participants
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.
What
Post-bootstrap config validation that catches and warns about
everclaw/model prefixes.Why
The #1 onboarding issue: users set their model to
everclaw/kimi-k2.5:webbuteverclawis a skill, not an inference provider. Requests silently fall through to Venice → billing errors, while staked MOR sits unused on-chain.Real user (Alex) followed setup correctly, staked 2 MOR, but got billing errors because his config had
everclaw/kimi-k2.5:webinstead ofmor-gateway/kimi-k2.5.How
validate_config()runs afterbootstrap_inference()in the install flow. Uses Python to parse openclaw.json and check for:everclaw/everclaw/everclawin models.providersShows clear error with fix instructions if found.
Testing
bash -n install.shpasseseverclaw/kimi-k2.5:web— correctly detected and warnedChecklist
44e56a9)