NewsHive
CONTACT USANALYST PORTAL →
aiBACKGROUND

<tool_call> write code in <think> --> failed

BACKGROUND
1 SIGNALFIRST DETECTED 22 March 2026UPDATED 21 April 2026
The NewsHive View

On March 22nd, a LocalLLaMA user reported a specific and quietly interesting failure: attempting to prompt a local language model to write code inside its `<think>` reasoning block — the scratchpad that models like DeepSeek-R1 and its derivatives use to work through problems before delivering a final answer — and finding that it simply didn't work. The post is sparse on detail, which is part of why the confidence sits where it does. But the observation touches something real. The `<think>` block was designed as a space for chain-of-thought reasoning, not as an execution or generation environment in its own right, and users have been probing its edges ever since these reasoning models started proliferating through the open-source community. Whether this was a model-specific quirk, a deliberate constraint, or something else entirely remains unestablished.

If confirmed, here is what this means. The boundary between a model's reasoning process and its output is not just a formatting convention — it reflects something architectural about how these models were trained and what behaviors they were rewarded for. If code generation is genuinely suppressed or degraded inside the thinking layer, that has real implications for anyone building agentic systems that try to use chain-of-thought reasoning as a lightweight execution environment, a pattern that's gained traction as developers look for ways to get models to self-verify or self-correct before committing to a final response. It also raises a sharper question about whether the `<think>` block is a window into genuine reasoning or a trained performance of it — and whether those two things can ever be fully separated.

Watch for follow-up posts on LocalLLaMA or Hugging Face forums where users test this across different model variants and quantizations, particularly any response from teams maintaining popular DeepSeek-R1 derivatives. A pattern across multiple models would change the picture considerably.

How the story developed
22 Mar
4.7
Other feeds and industry voices
24 Mar
Qwen 3.5 models create gibberish from large input texts?

<!-- SC_OFF --><div class="md"><p>In LM Studio the new Qwen 3.5 models (4b 9b 27b 122b) when analyzing large (more than 50k tokens) texts start to output gibberish. It is not a

OPINION · WHEN · LocalLLaMAOPEN STORY
14 May
Anthropic merges consecutive same-role messages, OpenAI doesn't (+4 tokens), anyone token-counted this on open-weight models?

<!-- SC_OFF --><div class="md"><p>I build context/harness optimization tooling, so provider-side serialization quirks actually matter to me. If you're optimizing over prompts, you

OPINION · WHAT · LocalLLaMAOPEN STORY
9 Apr
Gemma4 and Ollama: Native tool calling

<!-- SC_OFF --><div class="md"><p>Beginner here, now I have a good GPU and ollama using docker. Pulled the Gemma4 weights and was able to add it to cursor using ngrok. </p>

OPINION · WHO · LocalLLaMAOPEN STORY
15 Apr
Been trying to get Qwen 3.5 to stop reasoning using old methods like /no_think, it didn't work, but it said something like "too late" in its reasoning

<!-- SC_OFF --><div class="md"><blockquote> <p>Wait, I need to be careful about the &quot;no_think&quot; tag in the system prompt. The system prompt says <code>/no_think</code>.

OPINION · WHO · LocalLLaMAOPEN STORY
26 Mar
Nemo Code — Free Claude Code CLI alternative using NVIDIA's open models (one-command install, Docker sandboxed or local)

<!-- SC_OFF --><div class="md"><p>Built a free alternative to Claude Code ($20-$200/mo) that uses NVIDIA's open models through the same CLI framework (FREE!).</p> <p><strong>How

OPINION · HOW · LocalLLaMAOPEN STORY
23 Mar
Getting Stuck in Loops w Tool Calls

<table> <tr><td> <a href="https://www.reddit.com/r/LocalLLaMA/comments/1s1bjtr/getting_stuck_in_loops_w_tool_calls/"> <img alt="Getting Stuck in Loops w Tool Calls"

OPINION · WHAT · LocalLLaMAOPEN STORY
25 Mar
Can't get Continue to go through the code instead of simulating(hallucinating)

<table> <tr><td> <a href="https://www.reddit.com/r/LocalLLaMA/comments/1s3bxn2/cant_get_continue_to_go_through_the_code_instead/"> <img alt="Can't get Continue to go through the

OPINION · WHAT · LocalLLaMAOPEN STORY
26 May
ReAct tool-calling issue: Orchestration model computes internally instead of using tools

<!-- SC_OFF --><div class="md"><p>Built a local ReAct-style calculator agent with 6 tools:</p> <ul> <li>add</li> <li>subtract</li> <li>multiply</li> <li>divide</li>

OPINION · WHEN · LocalLLaMAOPEN STORY
Sources
LocalLLaMA

NewsHive monitors these sources continuously. All signal titles above link to the original reporting.

Intelligence by NewsHive. Need help navigating what this means for your business? Contact GeekyBee →