openclaw - 💡(How to fix) Fix /btw command fails with max tokens error: model[MiniMax-M2.7] does not support max tokens > 196608

Bug Description

Trigger: /btw command (e.g., /btw 你干嘛呢？)

Error:

⚠️ /btw failed: 400 {"type":"error","error":{"type":"invalid_request_error","message":"invalid params, model[MiniMax-M2.7] does not support max tokens > 196608 (2013)"}}

Observation: Normal chat works fine with the same model. Only /btw fails.

Root Cause

Investigation reveals that 196608 corresponds to the maxTokens of MiniMax-M2.5 in openclaw's provider catalog:

• MiniMax-M2.5 → contextWindow: 196608, maxTokens: 196608
• MiniMax-M2.7 → contextWindow: 131072, maxTokens: 131072 (as configured)

The /btw execution path appears to be using the wrong maxTokens value (196608 from MiniMax-M2.5) when sending a request for MiniMax-M2.7. The error message confirms the model is correctly identified as MiniMax-M2.7, but the max_tokens parameter is set to the MiniMax-M2.5 default.

This suggests that somewhere in the /btw execution path, model parameters are being resolved from the wrong model entry.

Environment

• OpenClaw version: ~2026.5.22
• Model: MiniMax-M2.7 via minimax-portal
• Channel: Telegram (and likely webchat)

Steps to Reproduce

1. Have an active session with MiniMax-M2.7 configured as the default model
2. Send /btw [any short text] in the session
3. Observe error: max_tokens > 196608 rejected

Expected Behavior

/btw should work identically to normal chat for the same model, using the correct maxTokens value (131072 for MiniMax-M2.7).