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@0.7.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

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 and 1.4.13 (the SDK stays 1.4.12; a newer CLI fingerprint starts with a recorded warning instead of failing). 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. 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):

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.