OpenCode
Run bots on OpenCode, using the providers you've already connected in OpenCode or an OpenCode API key.
When to use it
- You already use OpenCode and have providers connected there.
- You want one engine that reaches many providers through OpenCode's own settings.
- You want to run a local model with a full set of tools.
Install and sign in
Step 1
Find the engine
Open SettingsModels & enginesEngines and find OpenCode.
You're done when: you can see the OpenCode row and its status line.
Step 2
Install it
If it says Not detected, choose Open install in Terminal. Murage opens Terminal with this command ready to paste:
npm install -g opencode-ai
This needs Node.js and npm.
You're done when: the install command has finished without errors.
Step 3
Sign in
If OpenCode has no usable models yet, choose Open sign-in in Terminal and connect a provider. The command is:
opencode auth login
You can also connect providers in the OpenCode app itself.
You're done when: you finished the sign-in in the terminal.
Step 4
Check again
Back in Murage, choose Check again.
You're done when: the status reads Detected · signed in.
An OpenCode API key is optional. Murage detects your existing OpenCode Zen, Go and other provider connections on its own. If you prefer a key, Murage also reads it from the OPENCODE_API_KEY environment variable.
What works
- Tools: Murage's tools, including handing work to other bots, memory search, your own MCP servers, connected apps, the built-in browser, and cloud and local computers. Control of this computer is offered when OpenCode asks before each action.
- Pictures you attach go straight to the model, if the model accepts images.
- Model picking: Murage asks your OpenCode install for the models it can actually use, so the list matches what OpenCode sees. Local models from SettingsModelsLocal models appear too.
- Engine commands: type
/to see OpenCode's own commands, including/compact, next to Murage's.
Flux Router on OpenCode
The Flux Router tiers only work on OpenCode once Flux Router has been added as a provider in OpenCode's own settings. Murage never changes that file during a turn.
Local models on OpenCode
When you pick a local model for an OpenCode bot, Murage adds that server to OpenCode's own configuration file so OpenCode can reach it. If that file can't be rewritten cleanly, for example because it contains comments that a rewrite would lose, Murage refuses to change it and the turn fails with a message rather than damaging your settings.
Known limits
- Model list. OpenCode's model list is only as good as its provider setup. If OpenCode has no providers, Murage has nothing to offer.
- Voice needs its own keys. Voice calls need Flux Router credits or your own voice keys, whatever OpenCode uses.
Troubleshooting
You see
OpenCode has no usable modelsDo this
Run opencode auth login in a terminal, or connect a provider in the OpenCode app, then choose Check again.
You see
OpenCode returned no usable modelsDo this
OpenCode answered but listed nothing Murage can pick. Check your providers in OpenCode, then refresh the model list in Bot settingsModel.
You see
opencode CLI not foundDo this
Install OpenCode, restart Murage, or choose Set CLI… and pick the opencode program yourself.
You see
… has comments or trailing commas Murage can't keep, so it was left unchanged.Do this
OpenCode's configuration file allows comments, but Murage can't rewrite it without losing them. Remove them, or add the local server entry by hand, then try again.
You see
A local model fails on OpenCodeDo this
Test it first in SettingsModelsLocal models.