Summary

After using Command Code with Minimax M3, switching model to deepseek v4 pro, and then returning to Minimax M3, the chat fails with a 400 error. The queued message cannot be sent, and continue repeats the same error. Switching back to DeepSeek V4 Pro makes it work again, so this seems specific to Minimax M3.

Expected Behavior

The queued message should send normally after switching models regardless of the selected model.

Actual Behavior

Error: 400 invalid params, messages.73.content.1.tool_use.input: Input should be a valid dictionary (2013)

Steps to reproduce the issue

1. Start a Command Code session using Minimax M3.
2. Chat for a while until the context is large / compacted.
3. Switch model to DeepSeek V4 Pro.
4. Send a message successfully.
5. Switch back to Minimax M3.
6. Try sending the next queued message.
7. Observe the 400 invalid params error.
8. Run continue and observe the same error again.
9. Switch back to DeepSeek V4 Pro; the message works again.

Command Code Version

0.33.0

Operating System

Linux

Terminal/IDE

konsole

Shell

bash

Additional context

Model flow:

• Started with Minimax M3
• Switched to DeepSeek V4 Pro
• Switched back to Minimax M3
• Error occurred only on Minimax M3
• Switching back to DeepSeek V4 Pro worked

Error log:

Error: 400 invalid params, messages.73.content.1.tool_use.input: Input should be a valid dictionary (2013)

Type "continue" to try again. If the issue persists, contact support: https://commandcode.ai/discord
Request ID: req_eff6ccb680bded90c8e051a6c3dbeee7

After running continue:

Error: 400 invalid params, messages.73.content.1.tool_use.input: Input should be a valid dictionary (2013)

Request ID: req_242b74619528329c0472352602cc6ee7

Screenshot: