MiniMax rejects existing sessions with tool history

[megamen32]

Description

Switching an existing tool-heavy session to opencode-go/minimax-m3 can fail with a provider 400:

invalid params, tool call result does not follow tool call (2013)

The same model works in a fresh session, so the failure appears to be triggered by historical tool-call/tool-result parts from the existing session.

Plugins

None required to reproduce.

OpenCode version

Current dev branch behavior.

Steps to reproduce

1. Create a session with a model that uses tools and run a few tool calls.
2. Continue the same session using opencode-go/minimax-m3.
3. Send another message.
4. MiniMax rejects the request with tool call result does not follow tool call (2013).

Screenshot and/or share link

Provider error observed from https://opencode.ai/zen/go/v1/messages:

{"type":"error","error":{"type":"bad_request_error","message":"invalid params, tool call result does not follow tool call (2013)","http_code":"400"}}

Operating System

Linux

Terminal

Web UI / OpenCode server

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• [Bug] OpenCode Go: minimax-m3 fails with "tool call result does not follow tool call" (2013) #32608: Same error — minimax-m3 fails with "tool call result does not follow tool call (2013)" when there is tool-call history in the session
• MiniMax M3 rejects sessions with prior tool-call history #32611: Same root cause — MiniMax M3 rejects sessions with prior tool-call history, same error code and reproduction steps

Please consider closing this issue and adding any additional context to one of those existing reports instead.

[megamen32]

Closing this as a duplicate of #32608. I moved the fix/PR link there and updated PR #32609 to close the canonical issue.