Repository navigation
fix(muse-proxy): resolve contributor model ids in direct mode (#2753) - #2762
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 2 minutes. View limit details
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 |
Phase 2 amendment for #2753 (Drew, 2026-10-30: "should use contributor and disable all other muse meta providers and replace with this") — the proxy half. The config half (contributor models in
muse-direct, other Meta doors disabled, route retargets) follows in a separate PR.What
resolveModelAndEffortinbin/muse-proxy.mjsnow understands contributor ids:muse-spark-1.3-contributor/muse-wonder-1.0-contributorresolve to their base model for lookup, then the resolvedbaseModelre-attaches-contributor, so direct mode sends the contributor id upstream on/v1/responsesverbatim.muse-wonder-1.0-contributor-high→ basemuse-wonder-1.0-contributor, efforthigh, fullNamemuse-wonder-1.0-contributor-high.Test
New unit test (stub Meta API): contributor + effort-suffix parse, contributor with default effort, and the plain-id no-rewrite guard, asserting the exact upstream
model/reasoningbodies. Full file on the laptop: 20/20 pass (19 prior + this one).Need help on this PR? Tag
@codesmith-botwith what you need.