Agent failed before reply: All models failed (4): minimax/MiniMax-M2.7: 400 {"type":"error","error":{"type":"invalid_request_error","message":"invalid params, messages must not be empty (2013)"},"request_id":"063f4f2b471bd96ceddb04aa623003d2"} (format) | minimax-portal/MiniMax-M2.5: 400 {"type":"error","error":{"type":"invalid_request_error","message":"invalid params, messages must not be empty (2013)"},"request_id":"063f4f30265b74cad0e0fd73f091ab9e"} (format) | minimax-portal/MiniMax-M2.5-highspeed: 400 {"type":"error","error":{"type":"invalid_request_error","message":"invalid params, messages must not be empty (2013)"},"request_id":"063f4f35c0199298a2a5b7db7b755ece"} (format) | minimax-portal/MiniMax-M2.5-Lightning: 400 {"type":"error","error":{"type":"invalid_request_error","message":"invalid params, messages must not be empty (2013)"},"request_id":"063f4f3a41fde9a8a12d4279d76b538e"} (format) | LLM request rej…. Please try again, or use /new to start a fresh session.

TL;DR

The issue can be resolved by checking and ensuring that the request parameters, specifically the messages, are not empty before sending the request to the MiniMax models.

Guidance

• Verify that the input messages are being properly passed and not empty when creating a new session.
• Check the request payload for any formatting issues or missing parameters that could be causing the "invalid params" error.
• Review the OpenClaw version 2026.4.26 release notes to see if there were any changes related to request parameter validation or handling.
• Test the request with a known valid input message to isolate the issue.

Example

No code snippet can be provided without more context about the specific implementation.

Notes

The issue seems to be related to a regression introduced in version 2026.4.26, as rolling back to version 4.20 resolves the issue. However, without more information about the specific changes made in the update, it's difficult to provide a more targeted solution.

Recommendation

Apply workaround: Modify the code to ensure that the request parameters are valid and not empty before sending the request to the MiniMax models, as this seems to be the most likely cause of the error.