Muse Code subscription provider plugin for OpenCode
Repo pgquiles/opencode-muse, read from GitHub 21 h ago. pgquiles has not joined Take My Repo.
pgquiles/opencode-muse is a public repo on GitHub by pgquiles. Muse Code subscription provider plugin for OpenCode. It declares the MIT license on GitHub. It is written mainly in TypeScript, has 11 stars and last changed on 2026-11-16. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-20.
In the maintainer's words. Shown from GitHub; Take My Repo does not keep a copy.
An OpenCode plugin that lets OpenCode (and therefore
OpenChamber) use a Muse Code subscription with
auth and inference staying entirely inside the official Muse Code CLI
(muse serve, via @muse-code/sdk).
No subscription credential is ever extracted, cached, or injected into OpenCode.
Add the published package to your project-level opencode.jsonc (or
opencode.json):
{
"$schema": "https://opencode.ai/config.json",
"plugins": ["opencode-muse@1.1.0"],
}OpenCode downloads and manages the public package, so users do not need to run
npm install or create an npm account. Sign in with muse login (see below),
restart OpenCode or OpenChamber if it was already running, and choose a Muse
model.
Compatibility fallback: Current OpenCode V2 documentation supports package
entries in plugins, but our earlier probes did not observe config-array
loading on OpenCode 2.1.3; the embedded OpenCode 2.0.32 flow was verified with a
project-local plugin file. If your OpenCode version ignores the package entry,
install the package locally and add this file under .opencode/plugins/:
npm install opencode-muse mkdir -p .opencode/plugins cat > .opencode/plugins/opencode-muse.js <<'EOF' export { default } from "opencode-muse"; EOF
Use either the plugins array entry or the shim file, never both.
Registering the same plugin twice makes OpenCode report Duplicate plugin ID: opencode-muse and mark it failed (observed on 2.2.5).
The locally packed package passed provider discovery and a text-turn smoke test. Muse models and a text turn were also confirmed in OpenChamber after restarting it. Verified Muse CLI versions are 1.4.12, 1.4.13, 1.4.14, and 1.4.20; the 1.4.14 SDK pin matches the 1.4.14 CLI fingerprint exactly, and newer CLIs (1.4.20 verified) start under the recorded fingerprint warning. See #21.
Sign in through the official Muse Code CLI before using the provider:
muse login
OpenChamber's current provider UI does not expose OpenCode plugin command
authentication methods, so this plugin does not promise a sign-in button. It
uses the Muse CLI's existing account/configuration through muse serve; it
never reads Muse credential files, exports tokens, or changes subscription
mode. Every Muse child process the plugin spawns (serve hosts, audio
transcription, CLI probes) gets a sanitized environment: META_API_KEY and
MUSE_CONTRIBUTOR_MODE are stripped — Muse prefers the key over the account
login, which would silently bill pay-as-you-go instead of the subscription —
and MUSE_NO_AUTO_UPDATE=1 is set so Muse never replaces its binary under a
running host. Everything else passes through untouched. If the CLI has no
usable model catalog, the provider remains a disabled
setup placeholder rather than advertising a model that will fail on use.
The billing lane is a plain process environment variable read once when the
plugin loads (it is not an opencode.json field — probed on OpenCode 2.1.4,
plugin options arrive empty):
| Value | Meaning |
|---|---|
| unset (default) | Request the Contributor lane, like the Muse TUI |
on |
Same as the default, explicit |
off |
Request the Standard lane |
# One session on the Standard lane: OPENCODE_MUSE_CONTRIBUTOR_MODE=off opencode # Persist it by exporting the variable in your shell profile # (e.g. ~/.bashrc, ~/.zshrc) before launching OpenCode/OpenChamber.
Restart OpenCode/OpenChamber after changing it; the lane is fixed when the
plugin loads. Anything else fails setup with a clear error instead of
billing the wrong lane. Confirm the requested lane in the startup log and
the billed lane with muse usage. See
#29.
Which tools execute a turn is a separate process-wide choice, also read once when the plugin loads:
| Value | Meaning |
|---|---|
| unset (default) | Muse tools: Muse's own prompt and tools run the turn (vetted path) |
muse |
Same as the default, explicit |
opencode |
OpenCode tools: Muse acts as the model while OpenCode executes tools |
# One session with OpenCode tools instead of Muse tools:
OPENCODE_MUSE_TOOL_BACKEND=opencode opencodeRestart after changing it. Anything else fails setup instead of silently
running the wrong backend. With opencode, the plugin points Muse at a
private per-session config whose prompt/toolset is a loopback MCP bridge;
approvalMode: "allowAll" lets Muse run without asking, so OpenCode's own
permissions become the only fence. Private state lives under the XDG data
directory; your real Muse config is never read or modified. See
#37.
By default the bridge selects approvalMode: "onRequest" for every Muse
session, so Muse asks through the bridge before side-effectful actions.
That forced mode overrides the permission profile you configured in Muse
itself (permissions.default_profile): selecting :unrestricted in Muse
had no effect on bridge sessions, and every network destination or shell
command prompted again. OPENCODE_MUSE_APPROVAL_MODE makes the posture
explicit. Like the other knobs it is read once when the plugin loads:
| Value | Meaning |
|---|---|
| unset (default) | onRequest — the historical forced mode, unchanged |
host-default |
Omit approvalMode; the Muse host's configured permission profile applies, exactly as in the native TUI |
onRequest / allowAll / promptUnmatched / denyUnmatched |
Select that host-defined mode explicitly ("select, never create") |
# Let your Muse permission profile (e.g. :unrestricted) apply to bridge sessions:
OPENCODE_MUSE_APPROVAL_MODE=host-default opencodeRestart after changing it. Anything else fails setup with a clear error
instead of silently running the wrong approval posture. The opencode
tool backend ignores this knob: OpenCode's native permission evaluation
stays its only fence. Approval prompts now also show what is being
approved — the destination (protocol://host:port), shell command, file
path, or process target — plus each choice's rulePreview, so distinct
approvals no longer look like the same prompt repeated.
muse voice transcribe route — voice mode is included in every
subscription plan — and the transcript enters the turn as declared text.
A clip that cannot be transcribed fails the turn loudly instead of being
silently dropped. See
#32.minimal … max, model-dependent, one way
until the model is reselected), and the TUI /effort command ("Switch model
variant", verified end to end) or a #variant model suffix
(opencode run --model muse/…#high) selects one explicitly. Unknown variants
fail the turn instead of guessing. See
#28.rulePreview, so distinct approvals are distinguishable at a
glance. Anything unrecognized is asked once more, then
denied — ambiguity never approves — and your message still runs as a
fresh turn instead of being eaten, so a re-asking model can never trap
the conversation. Queued prompts are answered
first-in-first-out with an echo of what was granted. See
#30.muse exec --json, transcript muse export) are not exposed
as OpenCode features; muse exec --output-schema answer-shaping stays
unwired because it would fork the turn pipeline (see #35).metamate). Only
muse usage confirms the billed lane, and unknown Contributor settings fail
closed instead of guessing. Contributor catalog rows bill the requested lane
like every other row. See Configuration and
#29.opencode/muse-spark-1.3-contributor-free),
not this plugin's model. It no longer resolves anywhere, so OpenCode keeps
retrying and the session appears stuck on "connecting". Pick the model under
provider Muse Code — muse/muse-profile-tbh-model-muse-spark-1.3 —
instead of any historical "contributor-free" entry in recent-model lists. See
#26.muse serve and MSP. Its subscription eligibility is separate from this plugin's CLI-mediated approach and has not been established by this project.pgquiles/opencode-muse is a public repo on GitHub by pgquiles. Muse Code subscription provider plugin for OpenCode.
It declares the MIT license on GitHub.
Its maker has not tagged a system, so it is unknown here. Its README says what it needs.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
Its last change on GitHub was on 2026-11-16. Take My Repo does not judge from that whether it is maintained.
Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.
Get up and running with Kimi, GLM, MiniMax, DeepSeek, gpt-oss, Qwen, Gemma and other models.
Faster than your agent alone. And better. A workflow plugin that takes a bug, idea or ticket to a verified pull request: specs, cross-model review by risk, live QA, receipts in your repo. Claude Code · Codex · Cursor · Droid · Grok Build · OpenCode · Muse Code.
A comprehensive OpenChamber GUI panel to inspect and manage Docker containers, Docker Compose stacks, images, volumes, networks, and system storage.

Orca lets you run a fleet of coding agents (e.g. Claude Code, Codex) with your own subscription. Available on desktop, mobile and remote runtime.
Guido's Helping Hand -- automatic processing pipeline for photographed pages of historical music books
End-to-end Optical Music Recognition for Gregorian chant square notation (vision-encoder-decoder trained on synthetic GABC data)
This page is also available as structured data, with the same sources and dates.
/api/v1/resources/gh/pgquiles/opencode-museTake My Repo has not tested this on your machine. Requirements come from the project's own documentation.