Test-Time Cognition Makes Post-Training/RL Data Collection Faster, Better, Cheaper
Across four benchmarks and 25 models, Test-Time Cognition (TTC) raises success rates significantly on hard tasks, the ones that carry the learning signal in post-training. That gain turns into concrete benefits for collecting post-training data: compared with the standard inference typically used in RL, TTC solves more unique tasks, collects more successful trajectories per hour of agent time, and does it for lower cost.
Voaige Research·
❦
Introduction
The bottleneck for frontier model improvement = high-quality data
Frontier model improvement depends on a scarce resource: high-quality data, especially attempts on challenging, near-frontier tasks that end up succeeding. This was true for the pre-training era, when the internet supplied a vast store of human-generated data that enabled ChatGPT and the AI boom that followed. It is still true today, but in a new form: in a process called post-training, models generate their own data by attempting hard tasks and learning from successful attempts.
The ability to produce successful attempts has become a key metric for every company with a stake in frontier model development: neolabs, RL environment companies, data labs collecting and grading trajectories, and frontier labs running reinforcement learning at scale.
High-quality data, especially successful trajectories on hard tasks, therefore defines the central bottleneck determining how quickly models can improve.
Test-Time Cognition (TTC), a cognitive architecture we are pioneering, adds active reasoning, structured search and problem-solving, and dynamic compute allocation to modern LLMs. We find that TTC exhibits characteristics that make it far more efficient source of high-quality data, in three ways:
TTC is model- and domain-agnostic, and we find that its gains hold across a wide range of settings and benchmarks, across a large number of models and trajectories:
Part I · Where value accrues
The 30,000-foot view: where value accrues in intelligence
Pre-training scales along three coupled inputs: compute, dataset size and model size. Performance improves as each grows only until one of the other two becomes the bottleneck. More compute cannot compensate indefinitely for too little data or an undersized model, just as more data cannot compensate for limited compute.
Of the three, dataset size is the hardest constraint. The internet supplied a vast corpus of human-written text whose quality could largely be taken for granted, but that corpus is finite. Villalobos et al. estimate that the stock of high-quality language data could be exhausted this decade. Compute can be built and models enlarged; new human-written training data cannot be produced at comparable speed.
High-quality data has always been the fuel of AI
01
–
The pre-training era: Learning from human-written text
FuelHuman-written internet data
EnginePre-training
OutcomeLarge language models
To achieve a distinct advantage:Get access to more data
02
onward
The post-training era: Learning from the model's own successful attempts
FuelSuccessful trajectories on frontier tasks
EnginePost-training / RL
OutcomeReasoning models
To achieve a distinct advantage:(1) Solve harder tasks, or (2) obtain higher success rates, on frontier tasks in RL environments
Figure 1. In both eras, high-quality data is what advances model capability. Pre-training learned from a finite store of human-written internet text; post-training learns from successful trajectories that models must generate themselves, on frontier tasks they solve only some of the time.
Post-training has a different bottleneck: searching for successful trajectories. These trajectories are its high-quality data. Where pre-training learned from text written by humans, post-training increasingly generates data from the models themselves: models attempt tasks, their outcomes are scored, and successful trajectories become the learning signal. The scarce resource is not the number of attempts, but successful attempts on tasks the model has not yet mastered.
Producing that data already consumes a huge share of the training budget. Across three frontier models, roughly half of allocated training compute goes to RL post-training, and that share is growing.
Most of that post-training compute is spent producing trajectories, not updating model weights. In Microsoft MAI-Thinking-1's largest RL job, 4,096 GPUs run inference to search for successful trajectories while 768 run the learner: 5.3 GPUs searching for every one learning.
RL post-training compute now rivals pre-training in scale
Figure 2. Across 3 frontier model releases from 3 different organizations, search for successful trajectories makes up a large proportion of training compute. From our research post and the MAI-Thinking-1 technical report.
As the bottleneck shifts from collecting internet-scale text to generating successful trajectories, value shifts with it. It accrues to whoever can produce high-quality post-training data reliably—the business at the center of the emerging RL industry.
Part II · The RL industry
The scale and breadth of the RL industry
Funding for RL environment and data companies has exceeded $2.85B across eight domains
Largest company in its domainOther companies
Figure 3. 90 RL environment and post-training data companies have raised $2.85B in funding collectively and span 8 diverse domains.Part III · Frontier tasks and beyond
Frontier tasks and beyond: the most impactful tasks
A benchmark is a collection of tasks, and a model does not simply pass or fail a task. Given the same task many times, a model succeeds on some attempts and fails on others. The share of attempts it gets right is its per-task success rate, anywhere from 0% to 100%.
Not every task is equally valuable for improving a model. A successful attempt on an easy task mostly confirms what the model already does well; a successful attempt on a task it rarely solves teaches it something new. The value of a task therefore follows a hierarchy set by its difficulty: beyond frontier > hard > medium > easy. Figure 4 places all 253 tasks in our four benchmarks in this hierarchy, by their success rate under standard inference, pooled across 22 model runs.
The harder the task, the more valuable it is for AI improvement
Figure 4. Tasks form a hierarchy of value for AI improvement: the harder the task, the more valuable it is, from easy tasks up to those beyond the frontier.
Under standard inference, 119 of the 253 tasks (47%) sit at the frontier: 72 medium and 47 hard. Another 59 tasks (23%) are beyond the frontier, and 35 of those are never solved in any attempt. The tasks at the top of this hierarchy are where post-training data is most valuable and, as the rest of this post shows, also where it is most expensive to collect.
Part IV · Test-Time Cognition
Test-Time Cognition improves success rate on frontier tasks
Standard inference is very inefficient on frontier and beyond-frontier tasks. Post-training distills search into a model's weights, so standard inference follows the paths the model has learned to favor. On frontier tasks, and on tasks beyond the frontier, sampling the model more times spends more compute on failures it has already found (Figure 5, left).
TTC solves hard tasks by searching efficiently
Standard inference
Test-Time Cognition (TTC)
FailureSuccessLocal search
Figure 5. On frontier and beyond-frontier tasks, standard inference keeps following the model's most likely paths, and so repeatedly produces the same failures. TTC searches efficiently instead to arrive at a successful trajectory.
The key to improving success rate on these tasks is search. The model can often solve them, but the solution lies off its most likely paths. Finding it means exploring at test time: spreading attempts across distinct, uncorrelated regions of the space of possible trajectories rather than retracing the same few (Figure 5, right).
Test-Time Cognition (TTC) is our initial implementation of search in LLMs. TTC adds active reasoning, structured search and problem-solving, and dynamic compute allocation, while keeping model weights and agent harnesses fixed. Searching efficiently in LLMs, exploring far enough beyond the model's default behavior without wasting compute on unproductive branches, is still an open problem, and TTC is our first step toward solving it. We collect data with TTC across four benchmarks and 25 model comparisons, and we find that TTC substantially improves performance on frontier tasks.
On a task-by-task basis, across all 4 benchmarks, we observe that TTC improves performance for the vast majority of medium and hard tasks, increasing the success rate by 1.61× for hard tasks and by 3.06× for tasks beyond the frontier, from 2.2% to 6.7%.
TTC significantly increases success rate for hard tasks
Baseline, per taskTTC improvementTTC regression
TTC benefits remain consistent across benchmarks and domains
TTC improvement over baseline
Figure 6. TTC provides gains for the vast majority of medium and hard tasks across 253 tasks from 4 benchmarks. Success rates are pooled across all baseline and TTC runs.
We observe that across many matched baseline-TTC comparisons, and across all 4 benchmarks, TTC lifts the average success rate on hard/beyond-frontier tasks by 1.44× to 2.31×, taking hard tasks and tasks beyond the frontier together (those the baseline solves less than 35% of the time).
This translates into three gains: Coverage (tasks solved that standard inference never solves), Speed (more successful trajectories collected per hour of agent time), and Cost (a lower cost for each successful trajectory).
Part V · Coverage
Test-Time Cognition expands the frontier of solvable tasks
TTC helps models “unlock” tasks that the baseline never solves, or solves only very rarely, even when given a high attempt budget.
These tasks provide the largest impact on model capabilities, since the first successful trajectory is what will kickstart the learning signal for the model during RL. This materially expands the frontier of frontier LLM capabilities.
We observe that TTC improves coverage across all 4 benchmarks. For most benchmarks, TTC is able to find at least one successful solution for ~8%-12% more tasks in that benchmark.
TTC solves harder tasks than standard inference
TTC solves more unique tasks, across domains
CodingTerminal-Bench 2.04.2/89more unique tasks solved+8% · 54.6 → 58.8 · average over 10 comparisons
Customer serviceτ-knowledge4.6/97more unique tasks solved+9% · 50.6 → 55.2 · average over 5 comparisons
Financial researchFinance Agent V20.4/27more unique tasks solved+2% · 19.4 → 19.8 · average over 5 comparisons
IT operationsITBench-AA2.6/40more unique tasks solved+12% · 21.8 → 24.4 · average over 5 comparisons
Figure 7. TTC unlocks previously unsolvable or rarely-solved tasks.
This also shows that models are actually capable of solving these hard tasks, but standard inference prevents them from reaching these hard-to-find solutions. This leads to concrete problems for frontier data collection, post-training, and RL: it limits the amount of useful training signal that these models receive.
Part VI · Speed
More successful trajectories per hour of agent time
The second gain is speed. Since the speed of collecting successful trajectories grows by 1/(success rate), hard tasks shoulder a disproportionate amount of total data collection time. This is further magnified by models naturally taking longer to solve hard tasks.
These factors result in stark consequences: Across all 253 tasks of the four benchmarks, hard tasks and tasks beyond the frontier account for only 42% of all tasks, but take up 88% of total agent execution time to collect a comparable amount of successful attempts per task: 24% for the hard tasks and 64% for those beyond the frontier.
TTC significantly reduces time-to-success on hard tasks
Baseline success rateTime to collect 1 success, baselineTime to collect 1 success, TTC
Figure 8. Across all 253 tasks from 4 benchmarks, hard tasks are 19% of the tasks but 24% of the agent time it takes to collect one success on every task, and tasks beyond the frontier are 23% of the tasks but 64% of the time. On the tasks both solve, TTC needs 62% less agent time-to-success in total, cutting time in every tier.
Any meaningful speedup has to come from the hard/beyond-frontier tasks, and that is where TTC delivers. Per hour of agent time, TTC collects 1.2× to 3.8× as many successful trajectories on hard/beyond-frontier tasks as standard inference on average, and 2.0× to 12× as many in the best comparisons (Figure 9). This means that a week-long data collection campaign can finish in less than 1 day in the best case.
TTC collects more successful trajectories per hour
CodingTerminal-Bench 2.0
3.8×faster on average1 week → 1.8 daysdata collection time
12×faster in the best model comparison1 week → 14 hoursdata collection time
10 comparisons · 10 faster
Customer serviceτ-knowledge
1.6×faster on average1 week → 4.3 daysdata collection time
2.0×faster in the best model comparison1 week → 3.6 daysdata collection time
5 comparisons · 4 faster
Financial researchFinance Agent V2
1.7×faster on average1 week → 4.1 daysdata collection time
7.8×faster in the best model comparison1 week → 22 hoursdata collection time
5 comparisons · 4 faster
IT operationsITBench-AA
1.2×faster on average1 week → 5.6 daysdata collection time
5.0×faster in the best model comparison1 week → 1.4 daysdata collection time
5 comparisons · 3 faster
Figure 9. Per hour of agent time, TTC collects 1.2× to 3.8× as many successful trajectories on hard/beyond-frontier tasks as standard inference on average on every benchmark, and up to 12× as many in the best comparison. This allows data collection campaigns to finish significantly faster.Part VII · Cost
Lower cost per successful trajectory on hard/beyond-frontier tasks
The third gain is cost. A collection budget concentrates on hard/beyond-frontier tasks just as agent time does, since every additional failed attempt costs money as well as time.
TTC reduces cost-to-success on hard tasks
Baseline success rateCost to collect 1 success, baselineCost to collect 1 success, TTC
Figure 10. Across all 253 tasks from 4 benchmarks, hard tasks are 19% of the tasks but 31% of the cost of collecting one success on every task, and tasks beyond the frontier are 23% of the tasks but 54% of the cost. On the tasks both solve, TTC costs 28% less in total.
Tasks beyond the frontier take 54% of the budget, and hard tasks another 31%. We find that TTC also reduces the cost-to-success significantly: setting a data collection budget of $1M for standard inference on hard/beyond-frontier tasks, TTC lowers the average cost by 39% to 64% on three of the four benchmarks, and by up to 58% to 88% in the best model comparison on every benchmark.
Cost savings on hard/beyond-frontier tasks
CodingTerminal-Bench 2.0
64%cheaper on average$1M → $364Kdata collection cost
87%cheaper in the best model comparison$1M → $134Kdata collection cost
10 comparisons · 10 cheaper
Customer serviceτ-knowledge
56%cheaper on average$1M → $443Kdata collection cost
80%cheaper in the best model comparison$1M → $205Kdata collection cost
5 comparisons · 5 cheaper
Financial researchFinance Agent V2
39%cheaper on average$1M → $612Kdata collection cost
88%cheaper in the best model comparison$1M → $124Kdata collection cost
5 comparisons · 4 cheaper
IT operationsITBench-AA
30%more expensive on average$1M → $1.3Mdata collection cost
58%cheaper in the best model comparison$1M → $419Kdata collection cost
5 comparisons · 2 cheaper
Figure 11. Relative cost savings: Given a $1M baseline budget, TTC collects the same amount of successful trajectories on hard/beyond-frontier tasks for significantly less cost in most cases.
Together with the coverage gain, this means TTC reaches more of the hard/beyond-frontier tasks and collects their trajectories for less.
Conclusion
TTC: The next frontier of model capability
Across 25 models, 4 benchmarks spanning diverse domains from coding to customer research, and more than 10,000 trajectories, Test-Time Cognition (TTC) consistently improves three key factors for frontier data collection, post-training, and reinforcement learning: coverage, speed, and cost for hard/beyond-frontier tasks.
This highlights both the limitations of standard LLM inference, as well as how farther we can still push these models with the right cognitive architecture. We believe that TTC will play a key role in the next stage of post-training and defining the next frontier of model capabilities, ultimately ushering in a new cognition era beyond pre-training and post-training.
Appendix
Breakdown by model comparison
Each of our 25 model comparisons pairs a baseline model run with a TTC system that uses that model, with a trajectory counting as a success only when it achieves full credit. When a TTC system composes multiple models, we compare it separately against each constituent model run alone, and define the hard/beyond-frontier regime (<35% success) relative to that comparison's baseline so every comparison is weighted equally. A benchmark's best comparison, the best case in Figures 9, 11 and 19, is the one with the largest saving, except that a composed system is eligible only in its comparison against its strongest constituent, the one with the highest baseline average success rate. Figure 12 shows the resulting cost to collect 100,000 successful trajectories on hard/beyond-frontier tasks for every individual comparison on a logarithmic scale.
BaselineTest-Time Cognition (TTC)
Figure 12. Cost to collect 100,000 successful trajectories on hard/beyond-frontier tasks in each individual model comparison, baseline vs TTC (log scale). Each benchmark's figure in Figure 11 is the average of its rows; comparisons with few successes on these tasks are noisier.
While comparisons with very few baseline successes on hard/beyond-frontier tasks naturally exhibit more variance, TTC reduces collection costs in the vast majority of pairings, often by well over half.
Finally, we measure coverage directly. In each comparison, we take the tasks the baseline never solved in any of its attempts and count how many TTC solved at least once. Figure 13 shows this share of tasks rescued for every comparison.
Figure 13. Of the tasks each comparison's baseline never solved, the share TTC solved at least once. Each row shows how many of the baseline's never-solved tasks TTC rescued; the striped grey track is all of them. Because a single success counts, the share also depends on how many attempts each system made per task, which varies between runs.
TTC solves at least one previously unsolved task in 23 of the 25 comparisons, rescuing up to 58% of a baseline's never-solved tasks in a single comparison. The largest rescues come from TTC systems that compose multiple models, which can reach tasks that none of their constituent models solve alone. Averaged across comparisons, TTC rescues between 16% and 24% of never-solved tasks on each benchmark (Figure 14).
Figure 14. The share of the baseline's never-solved tasks that TTC solved at least once, averaged across each benchmark's model comparisons as in Figure 13. The striped track is all of the baseline's never-solved tasks.
Rescue tells only half of the story, since a system can also miss tasks that the other one solves. Figure 15 runs the same measure in reverse: of the tasks TTC never solved in a comparison, the share the baseline solved at least once.
Figure 15. The inverse of Figure 13: of the tasks each comparison's TTC system never solved, the share the baseline solved at least once.
TTC rescues more tasks than it loses in 15 of the 25 comparisons, and the two are even in three more. The difference comes mostly from TTC systems that compose multiple models, which rescue 114 tasks across their comparisons and lose 38. Single-model comparisons are closer to even, rescuing 44 and losing 40, as expected when a few attempts per task leave rarely solved tasks largely to chance. Averaged across comparisons, the baseline solves between 12% and 16% of TTC's never-solved tasks on each benchmark (Figure 16), against 16% to 24% in the other direction.
Figure 16. The share of TTC's never-solved tasks that the baseline solved, averaged across each benchmark's model comparisons as in Figure 15.
Dollar cost is not the only budget that limits trajectory collection. Agent execution time bounds how many trajectories a fixed pool of environments can produce, and environment steps, each interaction between the agent and its environment, measure the load placed on those environments. Using the time and steps logged for every trajectory, we measure both exactly as we measured cost: per successful trajectory on hard/beyond-frontier tasks, within each model comparison. Figure 17 shows the agent time spent per successful hard/beyond-frontier trajectory in every comparison.
BaselineTest-Time Cognition (TTC)
Figure 17. Agent execution time per successful trajectory on hard/beyond-frontier tasks in each model comparison, baseline vs TTC (log scale), measured as cost is in Figure 12.
TTC spends less agent time per successful hard/beyond-frontier trajectory in 21 of the 25 comparisons, about the same in one, and more in three. Averaged across comparisons, it cuts agent time per hard/beyond-frontier success by 20% to 74% on each benchmark, so TTC collects 1.2× to 3.8× as many successful hard/beyond-frontier trajectories per hour of agent time on average, and 2.0× to 12× as many in the best comparisons (Figure 9).
Environment steps show the largest savings of all. Figure 18 shows the number of environment steps spent per successful hard/beyond-frontier trajectory in every comparison.
BaselineTest-Time Cognition (TTC)
Figure 18. Environment steps per successful trajectory on hard/beyond-frontier tasks in each model comparison, baseline vs TTC (log scale), measured as cost is in Figure 12.
TTC needs fewer environment steps per successful hard/beyond-frontier trajectory in all 25 comparisons, and fewer than half as many in 23 of them. The savings compound: TTC attempts succeed more often on hard/beyond-frontier tasks and also tend to take fewer steps each. Averaged across comparisons, TTC cuts steps per hard/beyond-frontier success by 72% to 75% on each benchmark, so the same number of environment interactions yields between 359 and 398 successful hard/beyond-frontier trajectories for every 100 the baseline collects (Figure 19).
BaselineTTC, average over model comparisonsTTC, best model comparison
Figure 19. For every 100 successful trajectories the baseline collects on hard/beyond-frontier tasks, how many TTC collects for the same number of environment steps, averaged across model comparisons and in the best comparison, chosen as in Figure 9.
Figures 8 and 10 price each task per successful trajectory, which combines two things: how often an attempt succeeds, and what each attempt spends. Figures 20 and 21 isolate the second, on Terminal-Bench 2.0 alone. They show its 89 tasks, with the agent time and cost of a single attempt, whether it succeeds or not, pooled across runs as before.
Baseline success rateTime per attempt, baselineTime per attempt, TTCNever solved by the baseline
Figure 20. Figure 8 per attempt, on Terminal-Bench 2.0 alone: the agent time of one attempt at each task, solved or not. Per attempt, hard/beyond-frontier tasks take 57% of the baseline's agent time, against 90% per success on this benchmark, and the five tasks the baseline never solves take 53 minutes per attempt on average rather than unbounded time. TTC's attempts are faster on all 89 tasks, with 68% less agent time per attempt overall; its smallest cut is on hard/beyond-frontier tasks, which take 65% of what remains (third bar, drawn to scale).
Baseline success rateCost per attempt, baselineCost per attempt, TTCNever solved by the baseline
Figure 21. Figure 10 per attempt, on Terminal-Bench 2.0 alone: the cost of one attempt at each task, solved or not. Per attempt, hard/beyond-frontier tasks take 61% of the baseline's cost, against 91% per success on this benchmark, and the five tasks the baseline never solves cost $0.46 per attempt on average rather than an unbounded amount. TTC's attempts cost less on 74 of the 89 tasks and 41% less overall; its smallest cut is on hard/beyond-frontier tasks, which take 69% of what remains (third bar, drawn to scale).
Per attempt, the curves are far flatter than per success. A baseline attempt at a hard/beyond-frontier task costs about five times as much as one at an easy task ($0.83 against $0.17), while a successful trajectory on a hard/beyond-frontier task costs about fifty times as much ($11 against $0.21). Most of the concentration on hard/beyond-frontier tasks per success therefore comes from low success rates rather than from expensive attempts. On Terminal-Bench 2.0, TTC improves both factors: its attempts are cheaper and faster, and they succeed more often on hard/beyond-frontier tasks, which is why its savings per success (66% in cost, 81% in agent time) exceed its savings per attempt (41% and 68%).
✦
Continue exploring
Research on cognition, search, and more powerful adaptive intelligence.