Skip to content

feat(provider): merge upstream #11258 beta Muse Code support - #1

Open
devin-ai-integration[bot] wants to merge 3 commits into
mainfrom
devin/1789440851-muse-11258
Open

devin-ai-integration[bot] wants to merge 3 commits into
mainfrom
devin/1789440851-muse-11258

Conversation

@devin-ai-integration

Copy link
Copy Markdown

What Changed

Merges upstream pingdotgg/t3code#11258 (codex/muse-code-provider, beta Muse Code provider via @muse-code/sdk) into this fork's main as a single merge commit. The upstream branch was 155 commits behind main; four conflicts were resolved:

  • apps/server/src/provider/Layers/ProviderService.ts — kept main's newer agentAccessSettings/project-settings routing and the Claude background-turn cursor persistence, plus Muse's forked-session cursor handling.
  • apps/web/src/connection/storage.test.ts — kept both main's GitHub routing permission tests and Muse's thread snapshot cache tests.
  • packages/contracts/src/settings.test.ts — kept main's default-permission tests and Muse's provider-settings tests.
  • pnpm-lock.yaml — took main's lockfile and regenerated with vp i (adds @muse-code/sdk@0.1.1).

Why

Bring native Muse Code support into the fork. Upstream pingdotgg#11258 targets main directly, unlike pingdotgg#11392 which is built on the unmerged orchestration-v2 branch (pingdotgg#2829).

Verification

  • Typecheck: server, web, contracts pass.
  • Focused tests: server Muse + ProviderService (8 files, 206 tests), web storage.test.ts (6), contracts settings.test.ts (130) all pass.
  • No browser/desktop/mobile pass done.

Checklist

  • This PR is small and focused (it's an upstream merge, ~9k lines)
  • I explained what changed and why
  • I included before/after screenshots for any UI changes (see upstream PR)
  • I included a video for animation/interaction changes (n/a)

Link to Devin session: https://app.devin.ai/sessions/0da2d13b759845ae99a28d2baabf5d7c
Open in Devin Desktop: https://app.devin.ai/desktop/session/0da2d13b759845ae99a28d2baabf5d7c?variant=devin
Requested by: @aminamos

cristianuibar and others added 3 commits September 11, 2026 19:27
Use the Muse SDK for sessions and model discovery, with native provider updates, permission handling, and text generation across T3 clients.

Refs: pingdotgg#5516
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@devin-ai-integration

Copy link
Copy Markdown
Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

@devin-ai-integration

Copy link
Copy Markdown
Author

Completed recorded local web verification of 412bedfda.

Muse settings: verified; new-thread setup issue found
  • PASS: Muse Code is Beta and disabled by default.
  • PASS: Enabling without the CLI shows Not found, install/muse login guidance, and 0 models.
  • PASS: Refresh, reload persistence, and repeated on/off toggles; no console errors or uncaught page exceptions.
  • FAIL: New thread offers no Muse picker, says "Enable a provider," and its setup button opens disabled Antigravity rather than Muse.
  • Not tested by request: installed-CLI model discovery and real turns. No Muse CLI installed.
Default disabled Enabled / missing CLI
Muse Beta disabled Muse installation guidance
New-thread fallback Setup opens Antigravity
Generic provider prompt Wrong provider destination
Environment caveat

Original Chrome 133 rendered the provider list black. The unchanged app rendered correctly in Chrome 153, which was used for the completed flow. Original checkout's unrelated conflicted merge was preserved by testing a sibling worktree.

Devin session

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants