output content incorrectly routed into <think> tags instead of displayed as response

[shystab]

Description

在对话过程中（使用deepseekv4pro），AI 的完整回答被包含在 ... 标签内输出，用户只能看到推理过程的背景，而看不到实际答案。只有手动检查消息原始内容才能发现答案被错误地路由进了推理通道。

Plugins

none

OpenCode version

1.18.2

Steps to reproduce

1. 在连续对话中（通常 10+ 轮以上，经历过 plan/build mode 切换）
2. 用户发送一个问题
3. 模型输出的消息中， 标签内包含了本应是最终回答的内容
4. 标签外部的用户可见部分为空或不完整

Screenshot and/or share link

https://opncd.ai/share/CPx4zGkR

Operating System

Ubuntu 24.04

Terminal

vscode

[github-actions]

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

• Support parsing <think> and <thinking> tags as reasoning blocks #11439: Support parsing <think> and <thinking> tags as reasoning blocks — covers the same area of think-tag parsing and routing of content through reasoning vs. response channels
• v1.17.18: thinking leaks as literal text + TypeValidationError on usage (undefined) in message_delta (minimax-coding-plan/MiniMax-M3, Fedora/Kitty) #36387: thinking leaks as literal text — similar symptom (think tag content and response content crossing channels) with a different provider
• OpenAI Chat parser treats standalone </think> before tool_calls as assistant text #34126: OpenAI Chat parser treats standalone </think> before tool_calls as assistant text — related parser issue with think tag boundary handling

If your issue is distinct (response content being swallowed into the think channel rather than think content leaking out), please clarify and link to your share link so maintainers can differentiate.

[shystab]

Correction: the version is v1.14.22, not v1.18.2 (I edited after creation but couldn't change the version field).

The problem happened in the later part of the conversation (after ~30+ rounds, with multiple plan/build mode switches). The share link https://opncd.ai/share/CPx4zGkR shows this — scroll to the bottom messages where the response is wrapped in think tags instead of being displayed as visible output.

This is distinct from the linked issues:

• Those issues: think content leaks OUT (user sees things they shouldn't)
• This issue: response content is swallowed INTO think (user misses things they should see)