Engine connection problems

A network problem between the engine and its provider. Check you are online, then Retry. On a VPN or office network, check the provider's address is allowed through.

The sign-in has expired or the key is wrong. For an engine with its own sign-in, run it again in a terminal (claude auth login, codex login --device-auth), then choose Check again in SettingsEngines. For a key, replace it in SettingsModels.

The provider is rate limiting you. Wait a minute. If it is a plan limit, see Plan limits and backup engines.

The provider answered with something the engine did not expect. Retry. If it keeps happening with one model, try another model and check the engine's own logs.

The engine reported a failure without a reason. Retry. If it repeats, run the engine on its own in a terminal with the same model, and send a diagnostics report.

The engine refused the request before sending it. Retry, then check the engine's logs.

The provider turned the engine's sign-in down. Sign in through the engine's own command in a terminal, for example claude auth login or codex login --device-auth, then choose Check again in SettingsEngines. The mark clears on its own after 15 minutes or on the next good turn.

Replace the key in SettingsModels, or sign in again if that provider uses a sign-in.

Open SettingsModels, choose Replace key in the Flux Router card, paste a current key from your Flux Router account, and choose Test connection.

Something else was saved in the Flux Router field, often a key from another provider. Choose Fix the key and paste one that starts with sk-flux-.

Sign in with Flux Router opens your browser and waits for it to come back. If the browser did not open, or the sign-in page never returned, paste your Flux Router key in the field below the button instead. The same fix covers Could not open your browser. Paste your key instead., Could not start the local sign-in listener. Paste your key instead. and Flux Router did not complete the sign-in. Try again, or paste your key instead.

Your build has no browser sign-in for Flux Router. Paste the key.

Murage asks each engine for its version when it looks for it. The computer was too busy to answer in time. Wait a moment, then choose Check again.

You chose Set CLI… and the program you picked did not answer a version test. Check it is the engine's real program (on Windows, a .exe or .cmd, not something inside WSL), or pick another. Changing the path reloads engines and interrupts running turns, so finish tasks first.

Murage could not launch your terminal app. Copy the command shown and paste it into a terminal yourself.

Press Stop and give it a moment. If the chat stays busy, quit and reopen Murage. Your conversation is kept.

The conversation has grown past what the model can hold and the engine could not shrink it. Start a new thread for the next job. The bot still has its memory.

Read what the bot did so far, then ask it to carry on from there.

Murage gives each bot its own copy of your engine's files. The copy was being prepared when the turn started. Give it a moment, then retry. Your own engine setup was left untouched.

That per-bot folder could not be prepared. Check the disk has space and that Murage can write to its data folder, then retry.

Murage gives each bot its own copy of your engine's settings. One of the setup files is not valid JSON, so the turn did not start. The card names the file. Open it in the engine's folder, fix or remove it, then retry. Murage does not touch your own engine setup.