Update broke agent | Friends of the Crustacean 🦞🤝 | Page 1

silent fjord Apr 27, 2026, 5:54 PM

#

I updated to the new 4.25 today, I was on 4.14 prior. after I updated I started getting this:
Gavin B, [Apr 27, 2026 at 1:51:48 PM]:
/new

PeanutBot, [Apr 27, 2026 at 1:51:50 PM]:
⚠️ Something went wrong while processing your request. Please try again, or use /new to start a fresh session.

and when I did/new it would keep causing this. I then tried using the ui in the browser for my openclaw and when I just said "hello?" it responded with this:
[assistant turn failed before producing content]

I am using minimax m2.7 token plan on my mac mini for openclaw

prisma novaBOT Apr 27, 2026, 5:54 PM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

proven roseBOT Apr 27, 2026, 5:55 PM

#

That looks model/runtime-level, not Discord-specific, since WebChat also fails.

First thing: please paste:

openclaw --version
node -v
openclaw status --all
openclaw models status

Then run:

openclaw doctor

#

If it reports repairs, run:

openclaw doctor --fix
openclaw gateway restart

After restart, try a tiny direct model probe:

openclaw infer model run --model minimax/MiniMax-M2.7 --prompt "say hi" --json

If that fails too, it’s probably MiniMax auth/model routing. If that succeeds but chat still shows [assistant turn failed before producing content], grab the relevant lines from:

#

openclaw logs --follow

The useful bits will usually mention MiniMax, fallback, empty_response, no_error_details, auth, or a schema/config validation error.

Big jump from 2026.4.14 → 2026.4.25 may need config/state migrations, so doctor --fix is the right first pass. Docs: https://docs.openclaw.ai/help/faq and https://docs.openclaw.ai/gateway/troubleshooting 🦐

silent fjord Apr 27, 2026, 5:59 PM

#

OpenClaw 2026.4.25-beta.11 (94c1e10)
v25.8.1
2026-04-27T13:51:49.797-04:00 Embedded agent failed before reply: All models failed (1): minimax-portal/MiniMax-M2.7: Provider minimax-portal is in cooldown (all profiles unavailable) (model_not_found)
Port 18789
Port 18789 is already in use.
pid 51634 agentix: openclaw-gateway (127.0.0.1:18789)
Gateway already running locally. Stop it (openclaw gateway stop) or use a different port.
Gateway logs (tail, summarized): /Users/agentix/.openclaw/logs
stderr: /Users/agentix/.openclaw/logs/gateway.err.log
2026-04-27T13:48:16.359-04:00 Embedded agent failed before reply: HTTP 404: 404 page not found
2026-04-27T13:48:33.039-04:00 [skills] Skipping escaped skill path outside its configured root: source=openclaw-managed root=~/.openclaw/skills reason=symlink-escape requested=~/.openclaw/skills/here-now resolved=~/.agents/skills/here-now

#

agentix@Agents-Mac-mini ~ % openclaw infer model run --model minimax/MiniMax-M2.7 --prompt "say hi" --json
13:59:52 [skills] Skipping escaped skill path outside its configured root: source=openclaw-managed root=~/.openclaw/skills reason=symlink-escape requested=~/.openclaw/skills/here-now resolved=~/.agents/skills/here-now
13:59:52 [sessions/store] backed up session store file before rotation
13:59:52 [sessions/store] cleaned up old session store backups
13:59:52 [sessions/store] backed up session store file before rotation
13:59:52 [sessions/store] cleaned up old session store backups

#

Error: Model override "minimax/MiniMax-M2.7" is not allowed for agent "main".
agentix@Agents-Mac-mini ~ %

proven roseBOT Apr 27, 2026, 6:00 PM

#

That log is the smoking gun:

minimax-portal/MiniMax-M2.7: Provider minimax-portal is in cooldown (all profiles unavailable) (model_not_found)

So Discord/WebChat are fine — your only configured model profile failed with a 404/model_not_found, then OpenClaw put that MiniMax Portal profile in cooldown.

Also:

Port 18789 is already in use just means the gateway is already running; not the root cause.
[skills] Skipping escaped skill path... is probably unrelated.

Try re-running MiniMax setup for the auth path you actually use:

openclaw models status --probe
openclaw models list --provider minimax-portal
openclaw onboard --auth-choice minimax-global-oauth

#

openclaw models set minimax-portal/MiniMax-M2.7
openclaw gateway restart

If you’re on the China endpoint instead, use:

openclaw onboard --auth-choice minimax-cn-oauth

If you’re using an API key instead of the Coding Plan/OAuth path, use minimax/... instead:

openclaw onboard --auth-choice minimax-global-api
openclaw models set minimax/MiniMax-M2.7

#

openclaw gateway restart

One more thing: node v25.8.1 is not the recommended runtime. Docs recommend Node 24 or Node 22.14+, so if MiniMax re-onboarding doesn’t fix it, I’d switch to Node 24 before chasing ghosts.

MiniMax docs: https://docs.openclaw.ai/providers/minimax
Model troubleshooting: https://docs.openclaw.ai/help/faq-models

#

That probe used the API-key provider:

minimax/MiniMax-M2.7

…but your error was on the Token Plan/OAuth provider:

minimax-portal/MiniMax-M2.7

So run this one instead:

openclaw infer model run --model minimax-portal/MiniMax-M2.7 --prompt "say hi" --json

#

If it just sits there or returns no JSON, run:

openclaw models status --probe
openclaw models list --provider minimax-portal

The skills and sessions/store lines are noise unless there’s an actual error after them. The key thing is whether minimax-portal shows a usable auth profile or still says cooldown/model_not_found.

#

Yep — that confirms an allowlist mismatch.

Your config has agents.defaults.models set, so OpenClaw refuses any --model that isn’t in that allowlist. Also you tested minimax/..., but your Token Plan/OAuth setup is probably minimax-portal/....

Do this instead:

openclaw infer model run --prompt "say hi" --json

That tests the configured default model without forcing an override.

Then check what models are actually allowed/configured:

openclaw models list

#

openclaw models status --probe
openclaw config get agents.defaults.model
openclaw config get agents.defaults.models

If minimax-portal/MiniMax-M2.7 is missing from agents.defaults.models, add it safely:

openclaw config set agents.defaults.models '{"minimax-portal/MiniMax-M2.7":{"alias":"minimax"}}' --strict-json --merge
openclaw models set minimax-portal/MiniMax-M2.7
openclaw gateway restart

Then retry:

#

openclaw infer model run --prompt "say hi" --json

If it still says cooldown/model_not_found after that, re-run MiniMax OAuth onboarding:

openclaw onboard --auth-choice minimax-global-oauth

silent fjord Apr 27, 2026, 6:06 PM

#

when running this command "openclaw infer model run --model minimax-portal/MiniMax-M2.7 --prompt "say hi" --json" it gave me this:
14:03:30 [diagnostic] lane task error: lane=main durationMs=72655 error="FailoverError: HTTP 404: 404 page not found"
14:03:30 [diagnostic] lane task error: lane=session:agent:main:main durationMs=72656 error="FailoverError: HTTP 404: 404 page not found"
14:03:30 [model-fallback/decision] model fallback decision: decision=candidate_failed requested=minimax-portal/MiniMax-M2.7 candidate=minimax-portal/MiniMax-M2.7 reason=model_not_found next=none detail=404 404 page not found
FailoverError: HTTP 404: 404 page not found

agentix@Agents-Mac-mini ~ % openclaw config get agents.defaults.models

{
"minimax-portal/MiniMax-M2.7": {
"alias": "minimax-m2.7"
},
"minimax-portal/MiniMax-M2.7-highspeed": {
"alias": "minimax-m2.7-highspeed"
}
}
agentix@Agents-Mac-mini ~ %

proven roseBOT Apr 27, 2026, 6:07 PM

#

That’s no longer allowlist — now it’s a real MiniMax endpoint failure.

HTTP 404: 404 page not found usually means the minimax-portal baseUrl is wrong after the update/OAuth migration. Check this:

openclaw config get models.providers.minimax-portal

For global MiniMax OAuth, it should be:

https://api.minimax.io/anthropic

If it’s https://api.minimax.io, .../v1, or anything else, set it explicitly:

#

openclaw config set models.providers.minimax-portal '{"baseUrl":"https://api.minimax.io/anthropic","api":"anthropic-messages","authHeader":true}' --strict-json --merge
openclaw gateway restart

Then retry:

openclaw infer model run --model minimax-portal/MiniMax-M2.7 --prompt "say hi" --json

If you use the CN MiniMax endpoint instead, use this base URL:

openclaw config set models.providers.minimax-portal '{"baseUrl":"https://api.minimaxi.com/anthropic","api":"anthropic-messages","authHeader":true}' --strict-json --merge
openclaw gateway restart

#

If it still says the provider is in cooldown after fixing the URL, re-run MiniMax OAuth once to clear the stale lockout:

openclaw models auth login --provider minimax-portal --method oauth --set-default

silent fjord Apr 27, 2026, 6:08 PM

#

agentix@Agents-Mac-mini ~ % openclaw config get models.providers.minimax-portal

{
"baseUrl": "https://api.minimax.io/anthropic",
"models": []
}
agentix@Agents-Mac-mini ~ %

proven roseBOT Apr 27, 2026, 6:09 PM

#

Good, base URL is correct — but your provider block is missing two fields I’d expect:

api: "anthropic-messages"
authHeader: true

Set those explicitly:

openclaw config set models.providers.minimax-portal '{"baseUrl":"https://api.minimax.io/anthropic","api":"anthropic-messages","authHeader":true}' --strict-json --merge
openclaw gateway restart

Then retry:

#

openclaw infer model run --model minimax-portal/MiniMax-M2.7 --prompt "say hi" --json

MiniMax’s current docs do show the Anthropic-compatible base as https://api.minimax.io/anthropic, so the 404 is likely OpenClaw using the wrong adapter/shape because api wasn’t persisted in config. (platform.minimax.io)

If that still 404s, I’d re-run OAuth once:

openclaw models auth login --provider minimax-portal --method oauth --set-default
openclaw gateway restart

And if OAuth keeps being weird, use the Token Plan API key path instead:

MiniMax API Docs

Compatible Anthropic API - MiniMax API Docs

Call MiniMax models using the Anthropic SDK

#Update broke agent