openclaw - 💡(How to fix) Fix MiniMax-only configuration still invokes claude-cli/codex-cli and can hang TUI/model execution [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#73350Fetched 2026-04-29 06:20:41
View on GitHub
Comments
2
Participants
3
Timeline
3
Reactions
0
Author
Timeline (top)
commented ×2closed ×1

With OpenClaw 2026.4.26 configured to use only minimax/MiniMax-M2.7, the TUI / agent execution path still invokes claude-cli and later codex-cli. The run becomes extremely slow or hangs, and related OpenClaw processes can consume high CPU.

Error Message

[agent/cli-backend] claude live session turn failed: provider=claude-cli model=claude-opus-4-7 durationMs=92374 error=FailoverError

Root Cause

With OpenClaw 2026.4.26 configured to use only minimax/MiniMax-M2.7, the TUI / agent execution path still invokes claude-cli and later codex-cli. The run becomes extremely slow or hangs, and related OpenClaw processes can consume high CPU.

Code Example

[agents/auth-profiles] read anthropic credentials from claude cli keychain
[agent/cli-backend] cli exec: provider=claude-cli model=opus promptChars=505
[agent/cli-backend] claude live session start: provider=claude-cli model=claude-opus-4-7
[agent/cli-backend] claude live session turn failed: provider=claude-cli model=claude-opus-4-7 durationMs=92374 error=FailoverError
[agent/embedded] embedded_run_failover_decision ... provider=openai model=gpt-5.5 ... fallbackConfigured=false timedOut=true
[agent/cli-backend] cli exec: provider=codex-cli model=gpt-5.5
[agent/cli-backend] cli watchdog timeout: provider=codex-cli model=gpt-5.5 noOutputTimeoutMs=9000

---

openclaw infer model run --local --model minimax/MiniMax-M2.7 --prompt ping --json
RAW_BUFFERClick to expand / collapse

Summary

With OpenClaw 2026.4.26 configured to use only minimax/MiniMax-M2.7, the TUI / agent execution path still invokes claude-cli and later codex-cli. The run becomes extremely slow or hangs, and related OpenClaw processes can consume high CPU.

Environment

  • OpenClaw: 2026.4.26
  • macOS: Darwin 25.4.0 arm64
  • Node.js: v24.11.1
  • Package manager path: pnpm global install
  • Configured default model: minimax/MiniMax-M2.7
  • openclaw models status --json reports:
    • defaultModel: minimax/MiniMax-M2.7
    • resolvedDefault: minimax/MiniMax-M2.7
    • fallbacks: []
    • allowed: [minimax/MiniMax-M2.7]

Expected Behavior

When the default model and allowed model list are MiniMax-only, OpenClaw should not invoke claude-cli, OpenAI embedded models, or codex-cli unless those are explicitly configured as fallbacks or enabled for that run.

Actual Behavior

The runtime logs show OpenClaw reading Claude CLI credentials and invoking Claude/Codex paths despite MiniMax-only model configuration:

[agents/auth-profiles] read anthropic credentials from claude cli keychain
[agent/cli-backend] cli exec: provider=claude-cli model=opus promptChars=505
[agent/cli-backend] claude live session start: provider=claude-cli model=claude-opus-4-7
[agent/cli-backend] claude live session turn failed: provider=claude-cli model=claude-opus-4-7 durationMs=92374 error=FailoverError
[agent/embedded] embedded_run_failover_decision ... provider=openai model=gpt-5.5 ... fallbackConfigured=false timedOut=true
[agent/cli-backend] cli exec: provider=codex-cli model=gpt-5.5
[agent/cli-backend] cli watchdog timeout: provider=codex-cli model=gpt-5.5 noOutputTimeoutMs=9000

A minimal local inference test also hangs:

openclaw infer model run --local --model minimax/MiniMax-M2.7 --prompt ping --json

During that test, openclaw-infer reached high CPU usage and did not return promptly.

Additional Observations

  • openclaw models status --json shows MiniMax as the only configured/allowed model.
  • ~/.openclaw/agents/main/agent/models.json contains a codex provider entry as well as MiniMax, even though the status command reports only MiniMax as allowed.
  • The issue appears to be in internal planner / cli-backend / failover routing, not in the user-selected default model itself.
  • Gateway startup also loads many bundled plugins and Feishu/channel components even for seemingly lightweight commands, but the main bug here is model routing violating the MiniMax-only expectation.

Impact

The terminal UI becomes very slow or appears stuck after input. OpenClaw can spawn long-running or high-CPU processes, requiring manual cleanup with pkill/kill -9.

extent analysis

TL;DR

The issue can be mitigated by ensuring that the codex provider entry is removed from the ~/.openclaw/agents/main/agent/models.json file to align with the MiniMax-only configuration.

Guidance

  • Verify that the ~/.openclaw/agents/main/agent/models.json file does not contain any entries for codex or other non-MiniMax models.
  • Check the OpenClaw configuration files for any fallback settings that might be invoking claude-cli or codex-cli.
  • Run the command openclaw models status --json to confirm that only minimax/MiniMax-M2.7 is listed as the default and allowed model.
  • Test the openclaw infer model run command with the --local and --model minimax/MiniMax-M2.7 options to see if the issue persists after making the necessary configuration changes.

Example

No code snippet is provided as the issue seems to be related to configuration rather than code.

Notes

The issue appears to be related to the internal planner and failover routing of OpenClaw, which is not correctly respecting the MiniMax-only model configuration. Removing the codex provider entry from the models.json file may resolve the issue, but further investigation into the OpenClaw configuration and startup process may be necessary.

Recommendation

Apply the workaround by removing the codex provider entry from the ~/.openclaw/agents/main/agent/models.json file, as this seems to be the most direct way to address the model routing issue violating the MiniMax-only expectation.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix MiniMax-only configuration still invokes claude-cli/codex-cli and can hang TUI/model execution [2 comments, 3 participants]