OpenAI Executive: Tools Like Codex, Only Two Months Left to Shine

marsbitPublished on 2026-08-09Last updated on 2026-08-09

Abstract

In a candid statement, OpenAI's product and platform lead, Thibault Sottiaux, predicts that tools like Codex will become "primitive" within 2-3 months. He highlights that the current paradigm of running AI agents (Harness frameworks) locally on laptops is hitting fundamental limits as next-generation models demand more from their environments. The core limitations are threefold: 1) Local hardware constraints on compute and memory when agents handle concurrent subtasks; 2) The impracticality of requiring machines to stay online for long-duration tasks; and 3) The inability of lightweight local setups to manage the massive parallel context and toolchains of advanced models. The solution, Sottiaux suggests, is a shift towards "cloud-native infrastructure." The future lies in "light local command, heavy cloud execution," where developers use their devices as control panels. Complex tasks like code refactoring, testing, and automation will be offloaded to dynamic, parallel cloud clusters (e.g., isolated sandbox containers), with results streamed back. This evolution is already underway, with examples like Anthropic orchestrating 16 Claude instances across 2000 cloud sessions to build a C compiler. The competition will thus move from raw model capability to which platform can most effectively unlock a model's full potential through sophisticated, system-level Harness engineering.

"In another 2-3 months, Codex will be a primitive tool."

This wasn't said by a competitor, but by Thibault Sottiaux, the current OpenAI General Manager of Product and Platform responsible for ChatGPT and Codex, who came forward and said it himself.

Recently, the Harness framework has gradually broken out of its niche. From developers to white-collar workers, people are widely adopting these Agent tools, enjoying the automation benefits brought by AI. Among these, OpenAI's Codex stands out as a top performer.

Yet at this juncture, OpenAI executives are already looking further ahead. The next step for AI Agents might involve another paradigm shift evolving from single-machine tools towards "cloud-native infrastructure."

The meaning behind Thibault Sottiaux's statement that "notebooks aren't enough anymore" is clear: we are using single-machine harnesses to drive the next generation of models that possess long-horizon reasoning and high autonomy. This "big shoes on small feet" model is nearing its limits.

As we know, so-called Harness refers to the suite of capabilities built around large models for context management, tool calling, state persistence, environment isolation, and error recovery. Currently, many developers are running Agents (e.g., via CLI, Cursor, Claude Code, or lightweight Agent logic) on their laptops to complete tasks.

Of course, more and more developers are also inclined to use multiple tools and models together: for example, using Fable 5 on Claude Code to write project documentation, then switching to Codex to execute with other models.

However, this approach will encounter three major physical bottlenecks when facing next-generation frontier models:

Compute and Memory Limitations: When an agent needs to execute 20 subtasks concurrently (like running tests, scraping data, and compiling a large project simultaneously), the local notebook's memory, CPU, and concurrent sandbox (Docker/VM) resources will be instantly overwhelmed.

Long-running Tasks Cannot Shut Down: Complex agent tasks may need to run for several hours or even days, requiring the user's notebook not to be shut down, disconnected from the internet, or closed. This is highly impractical from an engineering perspective.

Parallel Explosion of Context and Toolchains: Next-generation models will undoubtedly support extremely long contexts and highly concurrent reasoning. Local lightweight harnesses will struggle to handle context compression, state synchronization, and centralized log tracing among large-scale concurrent agents.

Faced with these challenges, signs of Agent tools transitioning towards heavyweight infrastructure and system design have actually been gradually emerging over the past few months.

For example, OpenAI's Codex currently offers cloud-based asynchronous execution support. After a user issues a command in the terminal, the task is sent to an isolated container (Sandbox Container) in the cloud to run autonomously, with the phone or laptop merely serving a command-and-control function.

Simultaneously, cloud-native micro-sandboxes are emerging: Cloud-based, high-speed sandbox infrastructure specifically designed for AI Agents, like E2B, Daytona, Fly.io, and Modal, can dynamically spin up hundreds of independent container environments for agents to run code and verify results in parallel.

Among top AI teams including OpenAI, Anthropic, and Cognition, engineers are beginning to shift their R&D focus from optimizing prompts to "writing system-level harnesses."

In February of this year, the Anthropic team showcased a case where 16 Claude instances running in parallel across 2000 cloud sessions wrote a C language compiler. This is a milestone for generative AI moving towards multi-agent collaboration in software engineering. Different Claude instances played different roles: 1 Architect Agent responsible for designing the Abstract Syntax Tree (AST), 4 Coding Agents responsible for different modules, 2 Testing Agents dedicated to writing unit tests, and 1 Audit Agent responsible for reviewing the code flow and security.

Lead researcher Nicholas Carlini pointed out: "Most of the effort was spent building environments for the model, test loops, and feedback infrastructure."

In the next two to three months, such agent workflows might become our daily routine.

Combined with Thibault Sottiaux's prediction, "lightweight local command, heavyweight cloud execution" will become the standard. Developer interfaces (like IDEs, Terminals, Web UIs) will completely transform into control panels. Truly computation-intensive tasks like code refactoring, test execution, and browser automation simulations will all be processed in parallel within dynamic cloud clusters, with only the final differences (Diffs) and log streams pushed back to the local machine.

The deep integration of models and harnesses might shift the competition from "whose model has stronger reasoning capabilities" to "whose model's potential is unleashed more thoroughly." Those agent frameworks that rely solely on running Python scripts and simple API calls on local computers are about to hit a hard ceiling.

This article is from the WeChat public account "Machine Heart" (ID: almosthuman2014), author: Zenan

Related Questions

QAccording to the article, why does OpenAI's executive Thibault Sottiaux believe that tools like Codex are becoming outdated?

AThibault Sottiaux believes that the current model of using local, laptop-based harnesses to drive next-generation models with long-term reasoning and high autonomy is reaching its limits. This 'mismatched' approach is becoming unsustainable due to computational power, memory limitations, inability to handle long-running tasks without keeping the machine on, and difficulties managing parallel contexts and toolchains.

QWhat are the three main physical bottlenecks mentioned that current local harnesses face with next-gen models?

AThe three main physical bottlenecks are: 1. Computational power and memory limitations when agents need to execute multiple concurrent subtasks. 2. The impractical requirement for local machines to stay powered on and connected for hours or days for long-running tasks. 3. The difficulty for lightweight local harnesses to handle the parallel explosion of contexts and toolchains, including context compression, state synchronization, and centralized logging for massively concurrent agents.

QWhat is the key shift in the focus of engineering teams at leading AI companies like OpenAI and Anthropic, as described in the article?

AEngineering teams at leading AI companies are shifting their focus from optimizing prompts to 'writing system-level harnesses.' This means they are now prioritizing the development of robust infrastructure and systems—such as environments, testing loops, and feedback mechanisms—to effectively deploy and manage advanced AI agents.

QWhat example does the article give to illustrate multi-agent collaboration in software engineering?

AThe article cites an example from Anthropic where 16 Claude instances ran in parallel across 2000 cloud sessions to write a C language compiler. In this setup, different Claude instances played specialized roles: one architect agent, four coding agents for different modules, two testing agents, and one auditing agent for code flow and security review.

QWhat does the article predict will become the standard model for AI agent development in the near future?

AThe article predicts that 'light local command, heavy cloud execution' will become the standard. The developer interface (IDE, Terminal, Web UI) will become a control panel, while computationally intensive tasks like code refactoring, running tests, and browser automation will be executed in parallel within dynamic cloud clusters, with results streamed back to the local machine.

Related Reads

Google's Decade-Long AI Power Struggle Concludes, Pichai Gracefully Consolidates Control

A decade of internal AI rivalry at Google has concluded with CEO Sundar Pichai consolidating power through a masterful, bloodless reorganization. The key moves saw Demis Hassabis, DeepMind's visionary founder, step down as CEO of Google DeepMind to become Alphabet's Chief Scientist, focusing on long-term AGI. Concurrently, Google's legendary technical leader Jeff Dean departed with his team to start a new venture, in which Google invested. This restructuring marks the end of a long-standing divide between the research-focused DeepMind and the product-oriented Google Brain. Pichai's strategy, beginning with their 2023 merger under Hassabis, gradually centralized control. While Hassabis gained public acclaim for Gemini's progress and a Nobel Prize, Pichai quietly elevated Koray Kavukcuoglu, a pragmatic engineering veteran, to oversee daily operations. The catalyst was mounting pressure in 2026 as Gemini's development timelines slipped, causing stock declines. Hassabis, more passionate about pure research and his AI drug discovery company Isomorphic Labs, grew weary of the commercial grind. His graceful "promotion" effectively removed him from operational control. Pichai handled both transitions with characteristic finesse: granting Hassabis a prestigious, future-focused role to prevent a defection to rivals (as happened with former DeepMind co-founder Mustafa Suleyman), and investing in Dean's new company to keep his pioneering work within Google's orbit. The outcome is a fundamental shift: control of Google's AI future has passed from brilliant scientist-visionaries to professional managers and engineers like Kavukcuoglu and Pichai himself. It signals Pichai's bet that the AI race has entered an industrial phase won by systemic execution, organizational efficiency, and stable delivery, rather than lone genius. The era of scientists directly managing core AI is over at Google, replaced by a machine-like division of labor where the CEO decides who decides.

marsbit1h ago

Google's Decade-Long AI Power Struggle Concludes, Pichai Gracefully Consolidates Control

marsbit1h ago

Conversation with Blockchain Capital Partners: The Next Bull Market May Be Right in Front of Us

In a recent Bankless podcast, Blockchain Capital partners Aleks Larsen and Spencer Bogart discussed the crypto market's evolution from infrastructure to applications. They noted that widespread stablecoin adoption has built significant on-chain liquidity, boosting revenues for lending and trading protocols. The partners defended the "buyback and burn" token model, explaining its current effectiveness in aligning incentives and establishing credibility with holders, despite past debates on capital efficiency. Addressing the sentiment divide in crypto, they highlighted positive catalysts like regulatory clarity and institutional entry, even during the bear market. Aleks compared the industry's current state to the 2003-2004 internet era—post-"broadband transition" with cheap block space, awaiting mainstream adoption through applications like stablecoins and prediction markets. They observed a shift from "fat protocol" to "fat application," where value now accrues more at the application layer than the base infrastructure, a sign of a maturing ecosystem. Drawing parallels to AI, they noted similarities in early hype cycles but emphasized crypto's transparent, token-driven market corrections versus AI's private market adjustments. On Real World Assets (RWA), Spencer projected stablecoin market cap to reach trillions by 2030, detailing its multiplier effect on on-chain economic activity. For stock tokenization, he outlined two approaches: permissionless but legally indirect models and compliant, direct ownership channels, suggesting they can coexist in "sidecar" models alongside pure DeFi. The conversation concluded that while the industry's ethos evolves with institutional adoption, crypto's core promise of upgrading global financial infrastructure for greater efficiency remains intact and is steadily progressing.

marsbit3h ago

Conversation with Blockchain Capital Partners: The Next Bull Market May Be Right in Front of Us

marsbit3h ago

Trading

Spot
活动图片