> Not sure if modern models "think" only by outputting <thinking> blocks
That's pretty much it - a small refinement to "Chain of Thought" prompting, where you tell the model explicitly in the prompt to "Think step by step" or similar, so it writes out more steps before giving a final answer, potentially catching some errors. The "thinking" models are tuned to do that without being prompted to, and to output the "thinking" markers around it, so they can be hidden from the user.
My question was more about more complex problems, which no seem to be multi-turn somehow, or maybe just the harnesses make it look that way.
I am curious what the drop in thoughput is for multi-turn answers, instead of one-shot. More in line with the current "agentic" use-cases.
Well at ≈15k tps, I think the bottleneck will not be the model (reasoning or tool calling), and attention will be shifted to the harness’ engineering again.
Probably, the usual initial suspects for “what makes computation slow” will become a focus point that needs to be optimized again: file access, network, etc.