fix(sdk): use Claude harness model identifiers#5365
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughUpdates Claude’s stable harness aliases and curated catalog, adds ChangesClaude alias catalog
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
Railway Preview Environment
|
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.
Problem
The Claude harness picks a model by sending a bare request value (an alias like
sonnet, or a canonical id likeclaude-fable-5), not aprovider/idstring. The catalog had drifted from what the harness actually accepts:fableandfable[1m]. The harness does not recognize the Fable model family under those ids, so selecting Fable could not resolve.[1m]long-context variants (default[1m],sonnet[1m],haiku[1m],fable[1m]) as if they were stable request values. They are context-hinted variants that a session exposes or drops as account entitlements and promotions change, so pinning them in the catalog is unreliable.Fix
Publish the stable request values the picker can always send, and let the runner widen a bare id to a hinted variant when that is the only one offered.
CLAUDE_MODEL_ALIASESnow:default,sonnet,haiku,opus[1m],claude-fable-5.claude-fable-5: it matches a live bare option exactly, and the runner resolves it toclaude-fable-5[1m]when that is the only variant on offer. The friendlyfable/fable[1m]forms are gone.claude_models.curated.jsontrimmed to the stable set; the curation note and thesync-model-catalogskill now explain the stable-bare-id-plus-runner-widening rule so the catalog does not get re-pinned to one session's hinted set.Tests
test_capabilities.pyandtest_model_catalog.pyupdated to assert the exact harness config values —claude-fable-5present, friendlyfableabsent, noprovider/-prefixed ids.