[BUG] Model response is incomplete !!!

[HappyVing]

Problem (one or two sentences)

使用 frontend-design skill ,生成一个深圳天气预报，html的

Context (who is affected and when)

Date/time: 2026-01-08T15:20:41.909Z
Extension version: 3.38.3
Provider: openai
Model: deepseek-chat

模型提供了文本/推理，但未调用任何必需的工具。这通常表明模型误解了任务，或在确定使用哪个工具时遇到困难。系统已自动提示模型使用正确的工具重试。

Reproduction steps

• windows
• vscode 1.107.1
• roocode 3.38.3

Expected result

Normal handling

Actual result

Model response is incomplete

Variations tried (optional)

No response

App Version

3.38.3

API Provider (optional)

DeepSeek

Model Used (optional)

deepseek-chat-3.2

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

Thank you for reporting this issue. I have investigated the codebase and understand what is happening here.

The error message you are seeing ("模型提供了文本/推理，但未调用任何必需的工具...") is displayed when the model provides text/reasoning but does not call any of the required tools. The system automatically prompts the model to retry with proper tool usage.

To better understand this issue and determine if there is a bug to fix or an improvement to make, I need some clarification:

1. Does this happen consistently? Does the model fail every time, or does it eventually succeed after retries?

2. Does this work with other models? Have you tried the same task (generating a Shenzhen weather forecast HTML with the frontend-design skill) using a different model like Claude or GPT-4? This would help determine if it is a DeepSeek-specific issue.

3. What is your frontend-design skill configuration? Could you share the contents of your skill file? The skill instructions may need adjustment for better compatibility with DeepSeek.

4. Are you using XML or Native tool protocol? Different models have different tool calling capabilities, and DeepSeek may work better with one format over the other.

5. What is the expected outcome? After the automatic retry, does the task eventually complete, or does it keep failing?

Please tag @roomote in your response with these details, and I will be happy to investigate further or propose a fix if a code change is needed.

[HappyVing]

How to configure XML tools in your profile’s advanced settings? I don't know where to configure them.

[HappyVing]

// Please share this file with Roo Code Support (support@roocode.com) to diagnose the issue faster
// Just make sure you're OK sharing the contents of the conversation below.

{
"error": {
"timestamp": "2026-01-08T15:32:49.282Z",
"version": "3.38.3",
"provider": "openai",
"model": "deepseek-chat",
"details": "模型提供了文本/推理，但未调用任何必需的工具。这通常表明模型误解了任务，或在确定使用哪个工具时遇到困难。系统已自动提示模型使用正确的工具重试。"
},
"history": [
{
"role": "user",
"content": [
{
"type": "text",
"text": "\n使用 frontend-design skill ,生成一个深圳天气预报，html的\n"
},
{
"type": "text",
"text": "<environment_details>\n# VSCode Visible Files\n\n\n# VSCode Open Tabs\n\n\n# Current Time\nCurrent time in ISO 8601 UTC format: 2026-01-08T15:20:10.927Z\nUser time zone: Asia/Shanghai, UTC+8:00\n\n# Current Cost\n$0.00\n\n# Current Mode\ncode\n💻 Code\ndeepseek-chat\n<tool_format>native</tool_format>\n\n\n# Current Workspace Directory (c:/ving/ai/测试场地/roo_vs_kilo/roo/test001) Files\nNo files found.\nYou have not created a todo list yet. Create one with update_todo_list if your task is complicated or involves multiple steps.\n</environment_details>"
}
],
"ts": 1767885611201
},
{
"role": "assistant",
"content": [
{
"type": "text",
"text": "我将使用 frontend-design skill 来生成一个深圳天气预报的 HTML 页面。首先，让我检查技能适用性。\n\n根据技能描述，frontend-design skill 用于创建独特、生产级的前端界面，具有高质量设计。这适用于构建网页组件、页面或应用程序。用户请求生成深圳天气预报的 HTML，这完全符合该技能的适用范围。\n\n现在我需要加载 SKILL.md 文件来遵循技能定义的流程。"
},
{
"type": "tool_use",
"id": "call_00_eannkB5XqIOVhpm6qw8dIrBN",
"name": "read_file",
"input": {
"files": [
{
"path": "C:/Users/ving/.roo/skills/frontend-design/SKILL.md"
}
]
}
}
],
"ts": 1767885618649
},
{
"role": "user",
"content": [
{
"type": "tool_result",
"tool_use_id": "call_00_eannkB5XqIOVhpm6qw8dIrBN",
"content": "File: C:/Users/ving/.roo/skills/frontend-design/SKILL.md\nLines 1-42:\n 1 | ---\n 2 | name: frontend-design\n 3 | description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.\n 4 | license: Complete terms in LICENSE.txt\n 5 | ---\n 6 | \n 7 | This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.\n 8 | \n 9 | The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.\n10 | \n11 | ## Design Thinking\n12 | \n13 | Before coding, understand the context and commit to a BOLD aesthetic direction:\n14 | - Purpose: What problem does this interface solve? Who uses it?\n15 | - Tone: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.\n16 | - Constraints: Technical requirements (framework, performance, accessibility).\n17 | - Differentiation: What makes this UNFORGETTABLE? What's the one thing someone will remember?\n18 | \n19 | CRITICAL: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.\n20 | \n21 | Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:\n22 | - Production-grade and functional\n23 | - Visually striking and memorable\n24 | - Cohesive with a clear aesthetic point-of-view\n25 | - Meticulously refined in every detail\n26 | \n27 | ## Frontend Aesthetics Guidelines\n28 | \n29 | Focus on:\n30 | - Typography: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.\n31 | - Color & Theme: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.\n32 | - Motion: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.\n33 | - Spatial Composition: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.\n34 | - Backgrounds & Visual Details: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.\n35 | \n36 | NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.\n37 | \n38 | Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.\n39 | \n40 | IMPORTANT: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.\n41 | \n42 | Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.\n"
},
{
"type": "text",
"text": "<environment_details>\n# VSCode Visible Files\n\n\n# VSCode Open Tabs\n\n\n# Current Time\nCurrent time in ISO 8601 UTC format: 2026-01-08T15:20:18.903Z\nUser time zone: Asia/Shanghai, UTC+8:00\n\n# Current Cost\n$0.00\n\n# Current Mode\ncode\n💻 Code\ndeepseek-chat\n<tool_format>native</tool_format>\nYou have not created a todo list yet. Create one with update_todo_list if your task is complicated or involves multiple steps.\n</environment_details>"
}
],
"ts": 1767885618907
},
{
"role": "assistant",
"content": [
{
"type": "text",
"text": "继续阅读技能文件的剩余部分。\n[Tool Use: read_file]"
}
],
"ts": 1767885621530
},
{
"role": "user",
"content": [
{
"type": "text",
"text": "[ERROR] You did not use a tool in your previous response! Please retry with a tool use.\n\n# Reminder: Instructions for Tool Use\n\nTools are invoked using the platform's native tool calling mechanism. Each tool requires specific parameters as defined in the tool descriptions. Refer to the tool definitions provided in your system instructions for the correct parameter structure and usage examples.\n\nAlways ensure you provide all required parameters for the tool you wish to use.\n\n# Next Steps\n\nIf you have completed the user's task, use the attempt_completion tool.\nIf you require additional information from the user, use the ask_followup_question tool.\nOtherwise, if you have not completed the task and do not need additional information, then proceed with the next step of the task.\n(This is an automated message, so do not respond to it conversationally.)"
},
{
"type": "text",
"text": "<environment_details>\n# VSCode Visible Files\n\n\n# VSCode Open Tabs\n\n\n# Current Time\nCurrent time in ISO 8601 UTC format: 2026-01-08T15:20:21.612Z\nUser time zone: Asia/Shanghai, UTC+8:00\n\n# Current Cost\n$0.00\n\n# Current Mode\ncode\n💻 Code\ndeepseek-chat\n<tool_format>native</tool_format>\nYou have not created a todo list yet. Create one with update_todo_list if your task is complicated or involves multiple steps.\n</environment_details>"
}
],
"ts": 1767885621615
},
{
"role": "assistant",
"content": [
{
"type": "text",
"text": "我需要继续读取技能文件的剩余部分。让我使用 read_file 工具来获取完整的技能文件内容。"
},
{
"type": "tool_use",
"id": "call_00_dHDH4DfkyouzUJ1bah34JgMU",
"name": "read_file",
"input": {
"files": [
{
"path": "C:/Users/ving/.roo/skills/frontend-design/SKILL.md"
}
]
}
}
],
"ts": 1767885625972
},
{
"role": "user",
"content": [
{
"type": "tool_result",
"tool_use_id": "call_00_dHDH4DfkyouzUJ1bah34JgMU",
"content": "File: C:/Users/ving/.roo/skills/frontend-design/SKILL.md\nLines 1-42:\n 1 | ---\n 2 | name: frontend-design\n 3 | description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.\n 4 | license: Complete terms in LICENSE.txt\n 5 | ---\n 6 | \n 7 | This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.\n 8 | \n 9 | The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.\n10 | \n11 | ## Design Thinking\n12 | \n13 | Before coding, understand the context and commit to a BOLD aesthetic direction:\n14 | - Purpose: What problem does this interface solve? Who uses it?\n15 | - Tone: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.\n16 | - Constraints: Technical requirements (framework, performance, accessibility).\n17 | - Differentiation: What makes this UNFORGETTABLE? What's the one thing someone will remember?\n18 | \n19 | CRITICAL: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.\n20 | \n21 | Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:\n22 | - Production-grade and functional\n23 | - Visually striking and memorable\n24 | - Cohesive with a clear aesthetic point-of-view\n25 | - Meticulously refined in every detail\n26 | \n27 | ## Frontend Aesthetics Guidelines\n28 | \n29 | Focus on:\n30 | - Typography: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.\n31 | - Color & Theme: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.\n32 | - Motion: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.\n33 | - Spatial Composition: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.\n34 | - Backgrounds & Visual Details: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.\n35 | \n36 | NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.\n37 | \n38 | Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.\n39 | \n40 | IMPORTANT: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.\n41 | \n42 | Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.\n"
},
{
"type": "text",
"text": "<environment_details>\n# VSCode Visible Files\n\n\n# VSCode Open Tabs\n\n\n# Current Time\nCurrent time in ISO 8601 UTC format: 2026-01-08T15:20:26.373Z\nUser time zone: Asia/Shanghai, UTC+8:00\n\n# Current Cost\n$0.00\n\n# Current Mode\ncode\n💻 Code\ndeepseek-chat\n<tool_format>native</tool_format>\nYou have not created a todo list yet. Create one with update_todo_list if your task is complicated or involves multiple steps.\n</environment_details>"
}
],
"ts": 1767885626392
},
{
"role": "assistant",
"content": [
{
"type": "text",
"text": "我需要读取技能文件的剩余部分，看看是否有更多内容。让我读取从第43行开始的内容。\n[Tool Use: read_file]"
}
],
"ts": 1767885630114
},
{
"role": "user",
"content": [
{
"type": "text",
"text": "[ERROR] You did not use a tool in your previous response! Please retry with a tool use.\n\n# Reminder: Instructions for Tool Use\n\nTools are invoked using the platform's native tool calling mechanism. Each tool requires specific parameters as defined in the tool descriptions. Refer to the tool definitions provided in your system instructions for the correct parameter structure and usage examples.\n\nAlways ensure you provide all required parameters for the tool you wish to use.\n\n# Next Steps\n\nIf you have completed the user's task, use the attempt_completion tool.\nIf you require additional information from the user, use the ask_followup_question tool.\nOtherwise, if you have not completed the task and do not need additional information, then proceed with the next step of the task.\n(This is an automated message, so do not respond to it conversationally.)"
},
{
"type": "text",
"text": "<environment_details>\n# VSCode Visible Files\n\n\n# VSCode Open Tabs\n\n\n# Current Time\nCurrent time in ISO 8601 UTC format: 2026-01-08T15:20:30.180Z\nUser time zone: Asia/Shanghai, UTC+8:00\n\n# Current Cost\n$0.00\n\n# Current Mode\ncode\n💻 Code\ndeepseek-chat\n<tool_format>native</tool_format>\nYou have not created a todo list yet. Create one with update_todo_list if your task is complicated or involves multiple steps.\n</environment_details>"
}
],
"ts": 1767885630184
},
{
"role": "assistant",
"content": [
{
"type": "text",
"text": "我需要使用 read_file 工具来读取技能文件的剩余部分。让我指定从第43行开始读取，但 read_file 不支持行范围。我将读取整个文件，但之前已经读取了前42行。让我再次读取整个文件以确保获取完整内容。\n[Tool Use: read_file]"
}
],
"ts": 1767885634331
},
{
"role": "user",
"content": [
{
"type": "text",
"text": "[ERROR] You did not use a tool in your previous response! Please retry with a tool use.\n\n# Reminder: Instructions for Tool Use\n\nTools are invoked using the platform's native tool calling mechanism. Each tool requires specific parameters as defined in the tool descriptions. Refer to the tool definitions provided in your system instructions for the correct parameter structure and usage examples.\n\nAlways ensure you provide all required parameters for the tool you wish to use.\n\n# Next Steps\n\nIf you have completed the user's task, use the attempt_completion tool.\nIf you require additional information from the user, use the ask_followup_question tool.\nOtherwise, if you have not completed the task and do not need additional information, then proceed with the next step of the task.\n(This is an automated message, so do not respond to it conversationally.)"
},
{
"type": "text",
"text": "<environment_details>\n# VSCode Visible Files\n\n\n# VSCode Open Tabs\n\n\n# Current Time\nCurrent time in ISO 8601 UTC format: 2026-01-08T15:20:34.502Z\nUser time zone: Asia/Shanghai, UTC+8:00\n\n# Current Cost\n$0.00\n\n# Current Mode\ncode\n💻 Code\ndeepseek-chat\n<tool_format>native</tool_format>\nYou have not created a todo list yet. Create one with update_todo_list if your task is complicated or involves multiple steps.\n</environment_details>"
}
],
"ts": 1767885634525
},
{
"role": "assistant",
"content": [
{
"type": "text",
"text": "我遇到了错误，因为我之前的响应没有包含工具调用。我需要重新开始。让我创建一个待办事项列表来跟踪任务步骤。\n\n首先，我将创建一个待办事项列表。\n[Tool Use: update_todo_list]"
}
],
"ts": 1767885638112
},
{
"role": "user",
"content": [
{
"type": "text",
"text": "[ERROR] You did not use a tool in your previous response! Please retry with a tool use.\n\n# Reminder: Instructions for Tool Use\n\nTools are invoked using the platform's native tool calling mechanism. Each tool requires specific parameters as defined in the tool descriptions. Refer to the tool definitions provided in your system instructions for the correct parameter structure and usage examples.\n\nAlways ensure you provide all required parameters for the tool you wish to use.\n\n# Next Steps\n\nIf you have completed the user's task, use the attempt_completion tool.\nIf you require additional information from the user, use the ask_followup_question tool.\nOtherwise, if you have not completed the task and do not need additional information, then proceed with the next step of the task.\n(This is an automated message, so do not respond to it conversationally.)"
},
{
"type": "text",
"text": "<environment_details>\n# VSCode Visible Files\n\n\n# VSCode Open Tabs\n\n\n# Current Time\nCurrent time in ISO 8601 UTC format: 2026-01-08T15:20:38.244Z\nUser time zone: Asia/Shanghai, UTC+8:00\n\n# Current Cost\n$0.00\n\n# Current Mode\ncode\n💻 Code\ndeepseek-chat\n<tool_format>native</tool_format>\nYou have not created a todo list yet. Create one with update_todo_list if your task is complicated or involves multiple steps.\n</environment_details>"
}
],
"ts": 1767885638247
},
{
"role": "assistant",
"content": [
{
"type": "text",
"text": "我需要先使用一个工具。让我使用 read_file 工具来读取技能文件的剩余部分。\n[Tool Use: read_file]"
}
],
"ts": 1767885641857
}
]
}

[hbb-git]

我本地也有类似的问题， 一般在roo 在调用工具的时候出现， 而且出现比较频繁。尝试工具kilo 之后正常的。 期望尽快解决，感谢。

[Tool Use: ask_followup_question]
你想查看哪个子目录？
[{"text": "查看 Project/ 目录", "mode": null}, {"text": "查看 Lads/ 目录", "mode": null}, {"text": "查看 Kernel/ 目录", "mode": null}, {"text": "查看 doc/ 目录", "mode": null}]

</minimax:tool_call>

模型响应不完整
模型在响应中未使用任何工具。这通常发生在模型仅提供文本/推理而未调用完成任务所需的工具时。详情

"error": {
"timestamp": "2026-01-09T09:18:13.796Z",
"version": "3.39.1",
"provider": "openai",
"model": "MiniMax-M2.1-AWQ",
"details": "模型提供了文本/推理，但未调用任何必需的工具。这通常表明模型误解了任务，或在确定使用哪个工具时遇到困难。系统已自动提示模型使用正确的工具重试。"