Fuigo
The engine that comes with Murage: always installed, and ready once you give it a model to think with.
- Flux Router: one key for 70+ models, plus the four Flux tiers. See Flux Router models.
- A model key in SettingsModels & engines: 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
Step 1
Find the engine
Open SettingsModels & enginesEngines and find Fuigo.
You're done when: you can see the Fuigo row and its status line.
Step 2
Give Fuigo a model
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 SettingsModels & engines and choose Add connection to paste another provider's key, or add a local model under SettingsModelsLocal models.
You're done when: a key or local model is saved.
Step 3
Check the connection
Choose Check connection.
You're done when: the status reads Included · connected.
Step 4
Pick Fuigo for a bot
Open a bot, go to Bot settingsModel, set the Engine to Fuigo and pick a model.
You're done when: the bot shows Fuigo and the model you picked.
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 settingsModel, 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 SettingsModels & enginesEngines, 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
- Needs a model. 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.
- Small models are slower. A small local model is slower and less reliable with tools than a hosted one. Murage tests local models before offering them to bots.
- Engine updates. If a release is outside what your Murage version supports, Murage says so and keeps the current engine.
Troubleshooting
You see
Fuigo has no credentialDo this
Add a Flux Router key in SettingsModels & engines, or run fuigo login in a terminal, then choose Check connection.
You see
Repair bundled FuigoDo this
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.
You see
Native Fuigo download or compatibility verification failedDo this
The update didn't pass its checks, so your current engine is unchanged. Check your connection and try again later.
You see
Finish or stop running tasks before updating an engine.Do this
Stop any running bot turns, then update.
You see
A model fails on FuigoDo this
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.