Microsoft page hints GPT-6.1 Sol reuses GPT-6 Sol's weights with fewer inference passes

A thread posted to r/singularity on October 6 claims Microsoft let slip something it did not mean to: that GPT-6.1 Sol runs on the same base weights as GPT-6 Sol and reaches its answers with two inference passes instead of three. The detail was read off a Microsoft page. Neither Microsoft nor OpenAI has confirmed it, and that gap is the story.

What the live page does say

Microsoft's own Foundry blog for GPT-6.1 Sol, published September 29 and still online, is silent on passes. It calls the model an upgrade to GPT-6 Sol that approaches GPT-6 Astra on agentic coding, computer use and professional work, accepts text and image inputs, and fits up to one million tokens of context. Global Standard pricing is $2.00 per million input tokens, $0.10 for cached input and $10.00 for output, with long-context rates doubling that. Microsoft frames the release around cost per task rather than capability in isolation, and asks developers to weigh quality, reliability and price together.

Why a pass count would matter

A pass is one trip through the network. In a looped transformer the same block is applied again and again, each loop feeding its intermediate result back in, as Sebastian Raschka explains. More loops cost more compute per token. If GPT-6.1 Sol really ran two passes where GPT-6 Sol ran three, the gain would be cheaper or faster inference at roughly the same quality, not a new model. That fits the signals around it. OpenAI's deployment-safety addendum says GPT-6.1 Sol shares the same types of data and training as GPT-6 Astra, and an independent analysis argues a looped architecture explains why it closes most of the gap to Astra. Read that way, the passes claim is a cost story dressed as a capability one.

What is not established

The figure is not in the Foundry post as it now reads, and Microsoft has not printed it anywhere else; one account describes a shorter Azure description that was later taken down. Even in the original thread the reading is contested, with some commenters treating the change as deliberate and others guessing it came from a slip in a listing. No weights, no architecture card and no third-party count of the passes exist. Fewer inference passes would be a genuine efficiency gain if true, but until a vendor states it, it stays a plausible reading of a page rather than a fact. The September 30 launch write-up covered what OpenAI did confirm at the time.