Fable 5 Returned, GPT-5.6 Was Hidden Behind a New Lineup, and Gemini 3.5 Is Delayed: The Race Has Become Almost Incomprehensible to Users
How can a user choose between Fable 5, GPT-5.6, and Gemini 3.5 when the model race becomes almost impossible to follow?
Choose among Fable 5, GPT-5.6, and Gemini 3.5 through a real use case, access, price, and stability rather than a confusing naming hierarchy.
What to watch for
Key takeaways
The working conclusion from “ToTheMoon tonight” is that this section clarifies the mechanism behind the topic and preserves a constraint that would otherwise be lost in an overly simple conclusion.
In the context of “Claude Code, Claude Sowork and various ways of working with Claude,” this criterion applies: the forecast can be tested through specific dates, company actions, and changes in the product or market.
The boundary of the “Claude Science: AI-Instrument for Scientific Purposes” case is defined by this point: the forecast can be tested through specific dates, company actions, and changes in the product or market.
The discussion of “How to deal with the AI agents” yields a practical test: the practical boundary is defined by the agent’s permissions, the visibility of its actions, its action log, and the ability to stop execution.
For the “Claude Fable 5 is reopened: What happened?” scene, the decisive point is this: a launch matters only when it changes access, quality, price, or user behavior in a real workflow.
The boundary of the “How the tokens flow in different models” case is defined by this point: this section clarifies the mechanism behind the topic and preserves a constraint that would otherwise be lost in an overly simple conclusion.
The practical meaning of “Sol, Terra, Luna: new ChatGPT-5.6” is that this section clarifies the mechanism behind the topic and preserves a constraint that would otherwise be lost in an overly simple conclusion.
The working conclusion from “Why is Google holding Gemini 3.5 Pro” is that this section clarifies the mechanism behind the topic and preserves a constraint that would otherwise be lost in an overly simple conclusion.
What this episode is about
Claude is available again, OpenAI divides GPT-5.6 into Sol, Terra, and Luna, Google restricts capacity, and tokens disappear within minutes. Technical progress continues, but the market’s main problem is that people have to manage versions, limits, and agents instead of simply solving a task.
Understanding AI agents today is harder than launching one. Every company has its own names, modes, limits, and interfaces. A model may be available in the morning, restricted in the evening, and restored several days later. The user becomes a manager of product experiments.
Fable 5 was reopened, but the shutdown already revealed dependency risk. A team may have moved a project to the model and then lost access. The return solves the current problem without guaranteeing the next release.
Tokens in Codex and Claude are consumed differently and sometimes disappear almost instantly. A nominal subscription explains the true cost of a large task poorly. The useful comparison is therefore not the plan price, but how much of the project can be completed before a limit and how much manual work remains.
OpenAI is releasing GPT-5.6 while creating a Sol, Terra, and Luna lineup: flagship, balanced, and fast versions. This may simplify internal economics, but it adds more names for a person to understand. The most powerful model does not necessarily receive broad access immediately.
Google is delaying Gemini 3.5 Pro and limiting use even among large partners because infrastructure is finite. In real work, separating tasks is sensible: run one project in Fable, another in Codex, and send quick operations to a cheap model. The winner of the race has not yet been determined. The user loses when product complexity grows faster than utility.
The winner of the race has not yet been determined. As a result, the user loses when product complexity grows faster than utility.
Episode transcript
The episode is in Russian; below is an English reading guide to the transcript (the full EN transcript is a machine translation). Voice matching applied to 94 segments: 45 identified, 2 mixed, 21 marked with ✓, and 26 unresolved.
Loading…