Opencode-go模型在Openclaw飞书中使用的问题

[A13788899580]

Description

1. Openclaw版本为2026.5.19，飞书Bot
   以下遇到的问题，在使用模型‘minimax/MiniMax-M2.7’之前及现在都没发生过；
2. 遇到问题如下

• 使用了模型‘opencode-go/glm-5’
  -- 模型回复的信息在飞书中不显示，由于我要求回复时同时发送Bark信息，所以我知道模型回复了，但在飞书中只提示‘已通过Bark信息通知’
  -- 通过‘minimax/MiniMax-M2.7’分析：可能GLM-5的输出格式/结构与飞书插件的流式卡片渲染不兼容
• 使用模型‘opencode-go/deepseek-v4-pro'
  -- 出现400错误,日志体现：
  400 Error from provider (DeepSeek): Messages with role 'tool'
  must be a response to a preceding message with 'tool_calls'
  -- 通过‘minimax/MiniMax-M2.7’分析：
  这是 deepseek-v4-pro 与 OpenClaw 的消息格式不兼容 问题。当对话上下文包含 tool 消息但没有对应的 tool_calls 时，deepseek-v4-pro 直接返回 400 错误。每次出错后 fallback 到 minimax/MiniMax-M2.7，导致响应变慢。

Plugins

Openclaw的飞书插件

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• OpenCode version is missing — please provide the exact version you are using
• Steps to reproduce is empty — please describe what you did to trigger these issues
• Operating System and Terminal are missing — system information helps us investigate

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

---

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

• [Bug/Robustness] 400 Error: InternalError.Algo.InvalidParameter due to unclosed tool_calls after interruption #22808: 400 error due to dangling tool_calls without a corresponding tool response message — matches your DeepSeek 400 error symptom
• [DeepSeek V4] reasoning_content not round-tripped — 400 error on multi-turn tool calls #24190: DeepSeek V4 multi-turn tool call 400 errors caused by missing reasoning_content round-trip (closed/fixed) — closely related to your deepseek-v4-pro issue

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

Feel free to open a new issue that follows our issue templates.