What are the key takeaways from “I can't believe they released this” on Theo - t3․gg?
Why OpenAI's 'Ultra' reasoning mode is a trap
Insights from the Theo - t3․gg episode “I can't believe they released this”, published July 14, 2026.
Frequently asked questions about “I can't believe they released this”
What is "I can't believe they released this" about?
In "I can't believe they released this" (Theo - t3․gg, July 2026), openAI's newly released 'Ultra' setting for models is fundamentally mislabeled and inefficient. It functions as a recursive sub-agent toggle rather than a true reasoning level, leading to massive token burn and potential account lockouts without providing proportional performance gains.
What does "Ultra (Reasoning Setting)" mean in "I can't believe they released this"?
In "I can't believe they released this", It is not an increase in raw intelligence, but a mechanism to delegate work. Because it defaults to the highest 'Max' reasoning level for all sub-agents, it causes massive token burn.
What does "Workflows" mean in "I can't believe they released this"?
In "I can't believe they released this", Workflows provide a roadmap for the model, defining phases like research, verify, and synthesize. This limits recursion and provides a hard finish line for tasks.
What does "Context Pollution" mean in "I can't believe they released this"?
In "I can't believe they released this", It forces models to process irrelevant background info, increasing costs and confusing the sub-agent. V2 implementations often suffer from this by passing the full history by default.
What does "I can't believe they released this" say about the 'Ultra' setting in Codeex is misclassified as?
In "I can't believe they released this", The 'Ultra' setting in Codeex is misclassified as a reasoning level and should be treated as a high-risk 'skill' toggle. Users are incorrectly assuming it provides higher intelligence when it actually just spawns recursive sub-agents.
What does "I can't believe they released this" say about recursive sub-agent spawning under Ultra can lead?
In "I can't believe they released this", Recursive sub-agent spawning under Ultra can lead to hitting your 5-hour limit in under 20 minutes. This behavior poses a risk of consuming weekly limits prematurely.
What is this episode about?
OpenAI's newly released 'Ultra' setting for models is fundamentally mislabeled and inefficient. It functions as a recursive sub-agent toggle rather than a true reasoning level, leading to massive token burn and potential account lockouts without providing proportional performance gains.
What are the key takeaways?
Insights from the Theo - t3․gg episode “I can't believe they released this”, published July 14, 2026.
The 'Ultra' setting in Codeex is misclassified as a reasoning level and should be treated as a high-risk 'skill' toggle. — Users are incorrectly assuming it provides higher intelligence when it actually just spawns recursive sub-agents.
Recursive sub-agent spawning under Ultra can lead to hitting your 5-hour limit in under 20 minutes. — This behavior poses a risk of consuming weekly limits prematurely.
Workflows represent a superior programmatic approach to multi-agent tasks compared to tool-call-heavy implementations. — Workflows provide a hard cap on agent activity, preventing infinite loops and runaway costs.
What concepts are explained?
Insights from the Theo - t3․gg episode “I can't believe they released this”, published July 14, 2026.
Ultra (Reasoning Setting): It is not an increase in raw intelligence, but a mechanism to delegate work. Because it defaults to the highest 'Max' reasoning level for all sub-agents, it causes massive token burn.
Workflows: Workflows provide a roadmap for the model, defining phases like research, verify, and synthesize. This limits recursion and provides a hard finish line for tasks.
Context Pollution: It forces models to process irrelevant background info, increasing costs and confusing the sub-agent. V2 implementations often suffer from this by passing the full history by default.
Who should listen to this episode?
Software engineers and power users of AI coding tools like Codeex.
This summary was generated by Yedapo and may contain inaccuracies. It does not represent the views of the original creators.
30-second answer
Why OpenAI's 'Ultra' reasoning mode is a trap
OpenAI's newly released 'Ultra' setting for models is fundamentally mislabeled and inefficient. It functions as a recursive sub-agent toggle rather than a true reasoning level, leading to massive token burn and potential account lockouts without providing proportional performance gains.
Bottom line
Avoid using the 'Ultra' setting in current AI coding environments, as it is an expensive, poorly implemented toggle that risks depleting your usage limits.
Understanding the distinction between reasoning levels and agentic workflows prevents unintentional token waste and account suspension.
Best moment
The explanation of why 'Ultra' is a toggle rather than a reasoning level clarifies the source of the inefficiency.
Three takeaways
If you only read this, you've got it.
1
The 'Ultra' setting in Codeex is misclassified as a reasoning level and should be treated as a high-risk 'skill' toggle.
Users are incorrectly assuming it provides higher intelligence when it actually just spawns recursive sub-agents.
2
Recursive sub-agent spawning under Ultra can lead to hitting your 5-hour limit in under 20 minutes.
This behavior poses a risk of consuming weekly limits prematurely.
3
Workflows represent a superior programmatic approach to multi-agent tasks compared to tool-call-heavy implementations.
Workflows provide a hard cap on agent activity, preventing infinite loops and runaway costs.
Get insights on every episode of Theo - t3․gg
Sign up free to unlock the full analysis, chapters, key concepts, and Ask AI.
Agentic Implementation Comparison
This table compares the current agentic architectures used in AI coding tools.
Subject
Takeaway
Why it matters
Caveat
Ultra (Codeex)
Recursive sub-agent trigger masquerading as a reasoning level.
Causes massive, uncontrolled token burn and inefficiency.
High risk of limit depletion.
Workflows (Claude Code)
Programmatic, phase-based execution flow.
Provides deterministic end-states and better cost control.
Requires deeper configuration knowledge.
V2 Sub-Agents
Overhauled agent communication with mailbox-style message passing.
Adds complex context sharing that often leads to noise.
Unfinished and potentially bloated.
Ultra (Codeex)
Recursive sub-agent trigger masquerading as a reasoning level.
Causes massive, uncontrolled token burn and inefficiency.
High risk of limit depletion.
Workflows (Claude Code)
Programmatic, phase-based execution flow.
Provides deterministic end-states and better cost control.
Requires deeper configuration knowledge.
V2 Sub-Agents
Overhauled agent communication with mailbox-style message passing.
Adds complex context sharing that often leads to noise.
Unfinished and potentially bloated.
One thing to do · 5min
Disable the 'Ultra' setting in your Codeex or ChatGPT app immediately.
Prevents catastrophic depletion of your rate limits while the implementation remains immature.
“The host discovered that hitting your 5-hour limit in just 20 minutes is a direct result of Ultra's recursive sub-agent behavior.”
Full Context
A 1-minute read.
The central claim of this analysis is that OpenAI’s 'Ultra' setting is a fundamentally flawed implementation that misleads users by presenting a recursive agent toggle as a reasoning level. This mislabeling is not just a UI preference; it creates a structural failure in how the model manages task completion and resource allocation. Because the Ultra setting forces recursive spawning of sub-agents—all operating at the maximum reasoning level—it triggers a massive, multiplicative increase in token usage that quickly forces users into rate-limit bottlenecks.
The core risk is that the current implementation of sub-agents lacks a deterministic exit condition. In contrast to Claude Code’s workflow-based architecture, which defines fixed phases and clear schemas, the Ultra implementation allows agents to spawn infinitely. This leads to a situation where the model can spin up hundreds of unnecessary sub-agents, effectively evaporating the user's weekly usage quota in a matter of hours. This architectural divergence highlights the difference between immature, tool-call-heavy agents and the more efficient, programmatic workflows that will eventually define the future of agentic AI.
Ultimately, the host argues that the industry is copying the wrong lessons from competitors. While the user interface design (such as effort sliders) is becoming standardized, the underlying implementation of these agentic layers is highly inconsistent. The current state of 'Ultra' should be viewed as an experimental 'skill' toggle rather than a production-ready reasoning setting, and users who value efficiency should wait for more stable, workflow-driven iterations before trusting their development environments to these recursive agent systems.
If you liked this
Save this summary
Export to Markdown, Obsidian, or Notion — a Pro feature.