Fuigo
The engine that comes with Murage: always installed, and ready once you give it a model to think with.
Fuigo is the engine that comes with Murage. It's installed with the app, so there's nothing to download and no Node.js or npm to set up. It's the engine new bots start on when it has a model to use, and the one the included Chief of Staff runs on by default.
Fuigo doesn't bring its own AI account. It needs a model to think with, from any of these:
- Flux Router: one key for 70+ models, plus the four Flux tiers. See Flux Router models.
- A model key in Settings → Models: Anthropic, OpenAI, OpenRouter, DeepSeek, Mistral, Groq or xAI.
- A local model on your computer or network. See Local models.
- Fuigo's own sign-in, if you already use Fuigo in a terminal (
fuigo login).
When to use it
- You don't have an AI coding tool installed and don't want to install one.
- You want one engine that can use any model: hosted, Flux Router or local.
- You want a bot that can do everything Murage offers: hand work to other bots, connected apps, the built-in browser, computers and pictures.
Set it up
- Open Settings → Engines and find Fuigo. Its status says Included · connect an AI provider until it has a model, and Included · connected after.
- If it needs a model, the card says Fuigo is included and shows the Flux Router key box. Paste a Flux Router key, or go to Settings → Models and choose Add connection to paste another provider's key, or add a local model under Settings → Models → Local models.
- Choose Check connection.
- Open a bot, go to Bot settings → Model, set the Engine to Fuigo and pick a model.
What works
- Tools: Murage's own tools are listed to Fuigo directly, including handing work to other bots, searching memory, your own MCP servers, connected apps, the built-in browser, computers (cloud, Local VM, your own VPS, and this computer with your approval) and image generation when an image provider is connected.
- Pictures you attach go straight to the model, as long as the model accepts images.
- Model picking: Flux Router tiers first, then your favorites, then models from your keys and local servers. Any key you've saved can be used, whatever style of API it speaks.
- Effort: in Bot settings → Model, the Effort row offers none, low, medium, high, xhigh and max. Leave it unset and the engine decides.
- Folder trust: when a bot works in a folder that brings its own instructions, tools or hooks, Fuigo asks before using them. You'll see a Trust this folder choice. Until you trust it, those folder files are left out.
- Engine commands: type
/in the message box to see Fuigo's own commands alongside Murage's.
Updates
Fuigo updates separately from Murage. In Settings → Engines, the Fuigo row shows the selected source, the installed version and the latest version:
- Check for engine updates looks for a new release.
- Update Fuigo installs it. Downloads are checked for integrity, your computer's architecture and compatibility before they're used. No Node.js or npm is needed.
- Use managed Fuigo switches from a Fuigo you installed yourself to Murage-managed updates. Murage won't replace your own installation until you choose this.
- Use previous managed version rolls back one update.
- Use bundled Fuigo goes back to the copy that shipped with Murage.
Managed updates are available on macOS, and on 64-bit Intel/AMD Windows and Linux. Elsewhere Murage keeps the bundled copy.
Known limits
- With no Flux Router key, model key, local model or Fuigo sign-in, Fuigo has nothing to think with, and new bots won't be put on it.
- A small local model is slower and less reliable with tools than a hosted one. Murage tests local models before offering them to bots.
- If a release is outside what your Murage version supports, Murage says so and keeps the current engine.
Troubleshooting
"Fuigo has no credential" Add a Flux Router key in Settings → Models, or run fuigo login in a terminal, then choose Check connection.
"Repair bundled Fuigo" The copy that came with Murage couldn't start. Reinstall the official Murage package; your workspace isn't deleted. If it keeps happening, report your Murage version, operating system and installer type.
"Native Fuigo download or compatibility verification failed" The update didn't pass its checks, so your current engine is unchanged. Check your connection and try again later.
"Finish or stop running tasks before updating an engine." Stop any running bot turns, then update.
A model fails on Fuigo Try the same model with Flux Auto to rule out the key. If the error names payment or credits, check the provider's billing, or your Flux Router balance.