Engine troubleshooting
Fix engine problems in Murage: an engine isn't detected, needs a sign-in, keeps asking you to sign in, or a model won't answer.
Murage can't find or use the engine
Murage looks for engines in the usual install places and in your terminal's settings. Desktop apps sometimes see a different setup than your terminal does.
You see
Not detectedDo this
- Open a terminal and run the engine's command on its own to check it works.
- Restart Murage after installing an engine.
- Open SettingsModels & enginesEngines, find the engine, and choose Set CLI… to pick its program yourself.
On Windows, point to a real .exe or .cmd file. An engine installed inside WSL isn't a Windows program, so Murage can't run it directly.
You see
Fuigo says it has nothing to think withDo this
Fuigo, the engine that comes with Murage, needs a model. Give it one of these:
- A Flux Router key.
- A model key in SettingsModels & engines.
- A local model under SettingsModelsLocal models.
Sign-in problems
You see
Sign-in requiredDo this
Installing an engine isn't enough. It has to be signed in. Murage uses the engine's own sign-in.
- Run the engine's sign-in command in a terminal, for example
claude auth loginfor Claude Code. During the welcome, Help me sign in shows the exact command. - Come back to Murage. It picks up the sign-in.
Don't paste a ChatGPT or Claude password into Murage. Sign in through the engine itself.
You see
401 UnauthorizedDo this
This usually means the same thing: the engine isn't signed in, or its sign-in expired. For Codex, check with codex login status, sign in again, then restart Murage.
You see
An engine keeps asking you to sign in, and you don't use itDo this
In the Inbox, choose I don't use that engine to turn it off. You can turn it back on in SettingsModels & enginesEngines.
Models and features
You see
A model failsDo this
- Refresh the model list in Bot settingsModel after you update an engine.
- Pick a model your account actually has access to.
- Try the same model in the engine on its own, in a terminal. If it fails there too, it's an account problem, not a Murage one.
You see
Choose Claude or an ACP engineDo this
A feature says it needs a different engine. Some features, like handing work to other bots, connected apps, computers or the browser, only work with engines that support them. Murage names what you need, as in this message.
Switch the bot's engine in Bot settingsModel.