[dezren39]

Phase 2 of #2753 (direct mode itself landed in #2759): wire the door into the fleet OpenCode config. Drew, 2026-10-30: "wire it up".

What

One new provider block, muse-direct, in .opencode/opencode.jsonc (+48 lines, nothing else touched):

• npm: "@ai-sdk/openai" — Responses-native, the shape the meta provider uses. NOT openai-compatible/chat: the chat-completions route is the one that returns client_attestation_denied for the minted key from non-CLI clients (verified live 2026-10-30); the Responses route answers it with bare Authorization.
• baseURL: "http://127.0.0.1:{env:MUSE_PROXY_PORT:-18747}/v1" and apiKey: "muse-local" — the same local-proxy pattern as the muse block: the placeholder is ignored by muse-proxy, whose /v1/responses passthrough swaps in the minted plan key. No real credential in config, no auth.json entry.
• Models muse-spark-1.3 and muse-wonder-1.0, carrying the reasoning-effort variant set the meta block defines for these model families (minimal…max).
• A comment above the block, in the file's existing style, stating the pool facts: this is the SAME single Meta Muse Code High Usage pool as meta (not a separate pool, not the assistant's subscription), reached via muse-proxy direct mode (key minted from the Muse CLI login), ~10 input tokens per call vs ~26k through the CLI harness.

Deliberately NOT done (per Drew's phase-2 scope): muse-direct is not in disabled_providers, no model routes or defaults change, and the muse provider block is untouched — routing stays Drew's call.

Validation

• JSONC parses (full-line-comment strip + JSON parse); the block reads back with the expected npm/name/models/variants.
• Deployment + end-to-end verification on the laptop (deployed config is hardlinked from this repo file) is reported on muse-proxy: direct mode — exchange the Muse CLI account token for the minted plan key and forward chat completions verbatim #2753: muse-proxy runs the merged direct-mode code under muse-proxy.service (:18747, egress unpinned, no META_API_KEY), and a throwaway OpenCode serve with the deployed config answers a content-verified session on muse-direct/muse-spark-1.3.

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[coderabbitai]

Warning

Review limit reached

You'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 4 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 6568fa98-4306-4255-8ebc-3b733fc3704a

Commits

Reviewing files that changed from the base of the PR and between 46ce9b9 and f615183.

Files selected for processing: 1

• .opencode/opencode.jsonc

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-30T14:08:24.317217Z	f615183	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.