feat(providers): add Muse Code - #51
Conversation
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Warning Review limit reached
Next review available in:48 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (59)
📝 WalkthroughWalkthroughThis PR adds Muse Code as a provider. It adds contracts, authentication, CLI execution, provider status checks, text generation, session safety, runtime gating, web settings, documentation, and manual deployment triggers. ChangesMuse Code provider integration
Estimated code review effort: 5 (Critical) | ~120 minutes Possibly related PRs
Suggested reviewers: Poem
✨ 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 |
Browser QA on the production build with Muse Code 0.1.0-R708.1:
   |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:b4cb428600
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| if (input.method !== "account" && input.method !== "api-key") return null; | ||
| return input.method === "api-key" | ||
| ? { | ||
| command: "muse", |
There was a problem hiding this comment.
When a Muse instance uses the supported binaryPath setting because muse is not on PATH, its health checks and turns use that configured executable, but both Connect flows still spawn the literal muse command here. Consequently, the provider can appear installed and usable while Meta sign-in and API-key setup fail to start; pass the target instance/configuration through the connector and resolve the same binary path used by MuseDriver.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:7bf653c5c6
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| driver !== MUSE_DRIVER_KIND || | ||
| providers.some( | ||
| (provider) => provider.driver === MUSE_DRIVER_KIND && provider.availability !== "unavailable", | ||
| ) |
There was a problem hiding this comment.
When a standalone Muse instance fails config decoding or driver creation, ProviderInstanceRegistryLive.ts emits the same availability: "unavailable" shadow used for an unregistered driver (see lines 137–192). If that is the only Muse instance, this predicate treats the entire driver as unsupported, causing both the provider settings row and add-instance option to disappear; the user therefore cannot see the reported failure or edit/delete the broken configuration. Gate Muse using an explicit server capability rather than the availability of its current instances.
Useful? React with 👍 / 👎.
Uh oh!
There was an error while loading. Please reload this page.
What Changed
T3CODE_MUSE_ENABLEDis explicitly enabled.Why
Aldo needs a Codex-quality Muse integration for an internal staging evaluation. Meta's CLI and guidance are still early, so the provider must remain unavailable in managed production and must not leak into an automatic relay or public nightly release.
UI Changes
Browser QA used the production build with the exact pinned Muse CLI (
0.1.0-R708.1) at desktop (1440x1000) and mobile (390x844). Verified the provider row, Beta badge, CLI version/auth status, Meta sign-in/API-key chooser, API-key flow, and additional-provider dialog. Mobile had no horizontal overflow and the browser console had no errors. Screenshots are attached in a PR comment.Verification
ProviderRegistry.test.tsafter the CI fixture update: 44 tests passedpnpm --filter t3 typecheckpnpm --filter @t3tools/web typecheckpnpm --filter @t3tools/contracts typecheckpnpm --filter @t3tools/scripts typecheckgit diff --check origin/mainLocal Node was 22.23.2 versus the repository's declared
^24.13.1; all commands above passed, and GitHub Actions remains the release gate.Deployment Boundary
Checklist