Controlling Reasoning Effort in LLMs

How modern AI models manage reasoning tasks. We explore how systems like GPT-5.6 and DeepSeek V4 toggle between low, medium, and high effort compute modes.

MiHiR SEN
MiHiR SEN
·4 min read
An in-depth article analyzing how large language models control their reasoning effort during inference. Highlighting models like GPT-5.6 and DeepSeek V4, the piece explains the mechanics of Reinforcement Learning with Verifiable Rewards (RLVR) and how adjusting compute allocation yields distinct reasoning modes.

The release of OpenAI's o1 model fundamentally changed how the industry approaches artificial intelligence inference. By introducing the concept of a reasoning model, developers shifted focus from generating immediate answers to producing an intermediate chain of thought. Nearly two years later, reasoning models are the standard. With the launch of models like DeepSeek V4 and the GPT-5.6 family, the new frontier is controlling the exact amount of effort these models expend on a given prompt.

Conventional large language models operate on a straightforward mechanism. They receive a prompt and immediately begin predicting the next token, outputting a direct response. Reasoning models operate differently. They are trained to generate an internal trace, effectively talking through the problem step by step before finalizing an answer. This process does not magically grant the model human logic. Instead, it structures the output, allowing the system to self correct and experience aha moments where it catches its own mistakes mid sentence.

The mechanism behind this behavior is heavily reliant on Reinforcement Learning with Verifiable Rewards (RLVR). In this training paradigm, a model is rewarded exclusively for arriving at the correct final answer on tasks with objective truths, like math or coding. The model is not explicitly taught how to write the reasoning trace. It simply learns that taking the time to outline steps leads to the correct answer, which yields the reward.

As these models have matured, developers realized that forcing a model to generate a massive reasoning trace for a simple question is a waste of compute. This led to the development of reasoning effort controls. By allowing users to toggle between low, medium, and high effort modes, developers can dictate how much computational power is allocated during the inference phase.

Different models implement this control in unique ways. In the GPT-5.6 Sol model, OpenAI provides discrete effort settings that dictate the maximum number of tokens the model is allowed to spend thinking. If the task is simple, a low effort setting forces the model to synthesize its thoughts quickly. For complex logic puzzles, a high effort setting gives the model a massive token budget to explore multiple pathways, backtrack, and verify its logic before answering.

Open weight models are adopting similar strategies. DeepSeek V4 utilizes a more continuous effort value, while models like Nemotron 3 Ultra and Kimi K2.5 rely on specific tagging systems. Often, this is managed through a <think> tag implemented at the tokenizer level. By passing specific control tokens, developers can explicitly turn the reasoning mode on or off, instructing the model to bypass the trace generation entirely if speed is the priority.

This modularity represents a crucial shift from training scaling to inference scaling. Historically, making a model smarter meant spending millions of dollars on more GPUs and larger datasets during the training phase. Inference scaling allows a smaller, cheaper model to punch above its weight class simply by spending more time computing the answer at runtime. Allocating more budget at inference has proven to be an incredibly efficient way to boost accuracy without retraining the underlying weights.

Another popular technique for inference scaling is self consistency. In this approach, a model is queried multiple times in the background. The system then evaluates the different reasoning traces and selects the most common final answer via majority vote. When combined with adjustable reasoning effort, self consistency allows developers to fine tune the exact balance between latency, cost, and accuracy. For a medical diagnosis application, a developer might max out the effort level and run self consistency across ten instances. For a basic customer service chatbot, they might disable reasoning entirely.

We are slowly moving away from manual toggles. The next logical step for the industry is automated effort selection, where a lightweight routing model evaluates the complexity of a prompt and dynamically assigns the appropriate reasoning budget. Until then, understanding how to manipulate these effort controls is an essential skill for anyone building applications on top of modern language models. The ability to dial compute up and down on a per prompt basis represents the new control plane for artificial intelligence, dictating not just the quality of the answer, but the economic viability of deploying these systems at scale.