Conversation
Support stock Muse 1.2.1-R2847.1 alongside 1.0.3-R2198.1: the exact single-version gate rejected every CLI invocation on machines with the newer host installed. Discovery now prefers newer qualified versioned binaries, and the help/MSP baselines, installer, verifier, and docs cover both builds. Fix launcher auth dispatch: the credential selector trailed the gateway auth subcommand, which clap rejects, so login/logout/auth set/auth status all exited 2. The launcher now emits --provider before the action and the gateway accepts the flag in either position. Integrate launch-scoped --yolo: forwarded to stock Muse for the TUI, exec, and resume with a stderr warning, and translated to host sandbox options for MSP serve where approval stays wire-selected. Recognize the model-free mcp subcommand (never gateway-backed, never confused with wrapper auth) and teach the argv scanner the local subcommand value flags. Update the offline parity harness for the v4 readiness contract, the gateway --provider flag, and Muse 1.2.1 task fan-out, with an end-to-end YOLO lane.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 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 |
Owner
Author
|
update |
Owner
Author
|
.. |
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.
Support stock Muse 1.2.1-R2847.1 alongside 1.0.3-R2198.1: the exact single-version gate rejected every CLI invocation on machines with the newer host installed. Discovery now prefers newer qualified versioned binaries, and the help/MSP baselines, installer, verifier, and docs cover both builds.
Fix launcher auth dispatch: the credential selector trailed the gateway auth subcommand, which clap rejects, so login/logout/auth set/auth status all exited 2. The launcher now emits --provider before the action and the gateway accepts the flag in either position.
Integrate launch-scoped --yolo: forwarded to stock Muse for the TUI, exec, and resume with a stderr warning, and translated to host sandbox options for MSP serve where approval stays wire-selected.
Recognize the model-free mcp subcommand (never gateway-backed, never confused with wrapper auth) and teach the argv scanner the local subcommand value flags.
Update the offline parity harness for the v4 readiness contract, the gateway --provider flag, and Muse 1.2.1 task fan-out, with an end-to-end YOLO lane.
Summary
Describe what changed and why.
Validation
List the commands or manual checks you ran.
Checklist
cargo fmt -p codex-transport -p muse-codex -p muse-codex-gateway -- --checkpasses.cargo clippy --workspace --all-targets --locked -- -D warningspasses.cargo test --workspace --all-targets --lockedpasses.bash tests/scripts/release-tooling-test.shpasses when release tooling changes.CHANGELOG.mdare updated when user-visible behavior changes.Security and compatibility impact
Explain any effect on authentication, data flow, supported Muse versions,
provider routing, release integrity, or tool-call behavior. Write
Nonewhenthere is no impact.