Controlling Reasoning Effort in LLMs
ibobev
65 points
6 comments
July 20, 2026
Related Discussions
Found 5 related stories in 522.2ms across 14,369 title embeddings via pgvector HNSW
- Thoughts on LLMs – Psychological Complications cdrnsf · 11 pts · March 24, 2026 · 62% similar
- EsoLang-Bench: Evaluating Genuine Reasoning in LLMs via Esoteric Languages matt_d · 84 pts · March 19, 2026 · 60% similar
- The LLM Critics Are Right. I Use LLMs Anyway JeremyTheo · 209 pts · July 16, 2026 · 57% similar
- Let's talk about LLMs cdrnsf · 153 pts · May 04, 2026 · 57% similar
- LLMs can be exhausting tjohnell · 152 pts · March 15, 2026 · 56% similar
Discussion Highlights (4 comments)
simonw
I'm amused by how the whole reasoning model thing feels like a formalization of the old "think step by step" prompting hack, which was discovered against GPT-3 two years after that model was first released. My favorite trick for controlling the reasoning level is the hack where you look at the output token stream and spot the token for "the model has concluded reasoning"... and then replace that with the tokens for "wait, but" and force it to keep going!
sva_
I recommend his book, "Build a Reasoning Model (From Scratch)", which is also linked in the article. https://sebastianraschka.com/books/#build-a-reasoning-model-...
razorbeamz
LLMs don't actually reason, they just create the illusion of reasoning by repeating things over and over.
cyanydeez
mmm, practically, llamacpp solved this with reasoning budget for tokens and a customized message. ive tailored my local models to match agent with a message that pushes to use subagents and context compression. it works pretty smoothly if theres proper vector and scope to the project. theres probably a way to also get it to record memories but ive not seen a memory system that includes spatial type reasoning which would create memories associated with file paths down to AST graphlike leaves. then we could include remembering details about the path. llamacpp also has a header for setting these that an intelligent harness could tailor per round message and budget. ideally you start with a small budget and expand based on some complexity criteria. alas, i want to build things not related to AI.