/
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 97.9% of its employees are now using Codex, up from ~40% in August 2025; non-developer Codex usage is up 137x for individuals and 12x within OpenAI

The Register Thomas Claburn

Context & Ripple Effects

Codex has progressed from an API for translating natural-language prompts into code, including technology used by GitHub Copilot, to an agent product offered to ChatGPT business tiers. OpenAI has since expanded its desktop capabilities with computer control, browsing, automation memory, plugins, and image generation.

The reported internal adoption follows OpenAI’s claim that Codex has surpassed 5 million weekly active users and that knowledge workers account for roughly a fifth of its users. The internal figures therefore matter less as a coding-tool metric alone than as evidence of use beyond engineering.

First-order effects

  • Codex becomes a near-universal internal work tool at OpenAI, giving the company a large employee base using and stress-testing the product across developer and non-developer workflows.
  • The sharp rise in non-developer usage strengthens OpenAI’s case for positioning Codex as a knowledge-work and automation product, not solely an AI coding agent.

Second-order effects

  • Rival coding-agent and workplace-AI vendors face added pressure to support broader task execution—browser, computer-control, and workflow capabilities—rather than compete only on code generation.
  • Enterprise buyers evaluating Codex can treat OpenAI’s internal deployment as a more relevant reference point for cross-functional adoption, while still needing to test whether those workflows transfer to their own systems and controls.

Third-order effects

  • If non-developer adoption persists, the AI coding-agent category may converge with general-purpose workplace agents: tools initially purchased by engineering teams could become shared automation layers across functions.
  • That convergence would shift competition toward integration, permissions, reliability, and governance across business workflows, rather than model quality for programming tasks alone.

The trend: AI coding agents are broadening into enterprise automation platforms as vendors seek adoption among knowledge workers as well as software developers.

Discussion

  • @steph_palazzolo Stephanie Palazzolo on x
    New w/ @leomschwartz @amir: The Trump admin has asked OpenAI to stagger the release of GPT-5.6 over security concerns. On Thursday, CEO Sam Altman told staff that the government will be approving access to GPT-5.6 customer by customer, a highly unusual approach. [image]
  • Chris Kraft Chris Kraft on linkedin
    Here's an interesting new paper from OpenAI on how #AI agents are transforming work.  —  Source: https://lnkd.in/...
  • Julian Brophy Julian Brophy on linkedin
    The shift from AI chat to agents is bigger than “better answers.”  It changes the unit of work from a conversation to a delegated outcome. …
  • @stokel Chris Stokel-Walker on bluesky
    If you are one of the 2.1% of OpenAI employees not using Codex, I want to speak to you www.theregister.com/ai-and-ml/ 20...