/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

OpenAI says Operator, its AI agent that can use the web to perform tasks, will soon use a model based on o3 after previously using a custom version of GPT-4o

Kyle Wiggers / TechCrunch :

TechCrunch Kyle Wiggers

Context & Ripple Effects

Operator was positioned as a browser-based automation feature before its release, making model choice central to how OpenAI executes multi-step web workflows. Its move now follows the launch of o3 and o4-mini for paid ChatGPT users and OpenAI's earlier effort to bring o-series reasoning into its developer platform.

The change also fits a product roadmap in which OpenAI said it needed to integrate its model lineup more smoothly before subsequent releases. Operator is a concrete test of whether that integration can carry from chat and APIs into action-taking software.

First-order effects

  • Operator will transition from its custom GPT-4o-based system to an o3-based model, changing the reasoning layer behind its web-task execution.
  • OpenAI gains a more unified path between its o-series model releases and its agent product, while Operator users may see different task behavior once the switch arrives.

Second-order effects

  • The move raises the importance of model selection for agent products: rivals building browser or workflow agents will be judged not only on automation interfaces but on the reasoning models that drive them.
  • For OpenAI, o3 adoption in Operator creates a feedback loop between agent use and model deployment, potentially making operational reliability a more consequential product criterion than standalone chat capability.

Third-order effects

  • If leading model providers increasingly pair reasoning models with tools that can act on the web, competition may shift toward tightly integrated, workflow-native agents rather than general-purpose assistants alone.
  • That trajectory makes controls over permissions, oversight, and failure handling more central to agent differentiation, especially as agents move from answering requests to executing multi-step tasks.

The trend: Frontier AI vendors are turning reasoning models into the execution engines for increasingly integrated, web-operating agents.

Discussion

  • @openai @openai on x
    Operator 🤝 OpenAI o3 Operator in ChatGPT has been updated with our latest reasoning model. https://operator.chatgpt.com/
  • @danshipper Dan Shipper on x
    holy shit the new operator is CRAZY here it is making copy edits in a Google Doc! [image]
  • @reiinakano Reiichiro Nakano on x
    we switched out the underlying Operator model to o3 today. we think it's a step jump improvement from the previous 4o-based model. give it a try with some of your old prompts that failed! it was fun to work on this, the o-series paradigm makes everything so much better!
  • @sama Sam Altman on x
    big improvement!