Codex

Sources#

Summary#

Codex is OpenAI's agentic coding and work platform — the OpenAI-side counterpart to Claude Code throughout this wiki. Released April 2025 as a command-line tool, it grew into a multi-surface agent harness: a threaded interaction model (independent per-task workspaces), reusable skills and installable plugins, a headless App Server Protocol for programmatic sessions, and the Symphony orchestrator that turns Linear into a control plane for it. Originally built for software development — a domain with verifiable, economically valuable, modular outputs — its usage has spread well beyond code into research, drafting, data analysis, and operations.

What it is, in this corpus#

The agent harness. Built on the GPT-5-series Codex models; runs multi-step, tool-using, file-modifying tasks. Its threaded model is what enables parallel agent orchestration — many independent agents at once.
The systematization layer. Skills (SKILL.md workflow specs) + plugins (installable bundles of skills, MCP integrations, hooks) are the substrate of Agentic Work Systematization; a skill authors a workflow, a plugin distributes it.
The headless protocol. The App Server Protocol (JSON-RPC over stdio) drives Codex non-interactively — the basis for orchestration and CI-style use.
The orchestrator. Symphony (OpenAI open-source, March 2026) coordinates per-issue Codex workspaces from a Linear board.
The usage subject. OpenAI's June 2026 Shift to Agentic AI study measures Codex adoption across individual, organizational, and OpenAI-internal populations — weekly-active usage up >5× in H1 2026, increasingly outside the developer base.

The desktop app (Ambrosino's account)#

The wiki's original Codex entry is the CLI + orchestration stack. Andrew Ambrosino's June 2026 interview describes the desktop app — a distinct surface with its own history and trajectory:

Timeline. The team started the app in November 2025, dogfooded it internally, and released it in February 2026. Ambrosino stresses it was a right-sized surface — "sort of a chatbot, but more than that; you could see the code but we weren't going to let you edit it" — deliberately not an IDE.
Usage (first-party, unverified). He reports ~90% of OpenAI's entire company (not just engineers) uses Codex, ~100% of employees weekly; 5M+ weekly active users, grown ~6× since January. vendor-claim-tier figures from a product leader.
From developer tool to general knowledge work. The pivotal internal discovery: non-engineers (marketing, comms, finance, legal) used the Codex app "even though it is actively hostile to these people" — showing them code, asking to run rg. Attempts to build separate general surfaces failed because "nobody would leave the Codex app." The strategy became one "home base" — start simple, grow complex per user, connect out to specialist tools (it talks to the Excel add-in for finance; opens other apps to finish work) — with the "super app" label Ambrosino says he regrets having to hear about.
Self-extension. The signature anecdote: OpenAI's in-house videographer edited launch videos with Codex, which — not being a video editor — built its own Premiere Pro extension to control Premiere by editing the backing files and then talking to the extension it wrote. The agent extends itself into a specialist tool it wasn't designed for.
Interaction-modality design. The app juggles connectors, an in-app browser (now on the Atlas "owl" stack with enterprise login), a Chrome-extension bridge, and computer use — Ambrosino calls choosing among them a live, unsettled design problem (keyboard-shortcut mapping, "browser at the top level vs. agent-only browser"). Computer use lets it "just start clicking" through UIs with no API (e.g. the Google Cloud console).
Automations as an OpenClaude-style operator. Ambrosino runs scheduled tasks that triage his ~3,000 Slack channels into a daily brief he steers in natural language — an emerging first-class pattern the team wants to make setup-free for non-builders.

The app is also the setting for Ambrosino's product theses: Implementation Abundance Inverts Product Work, "the February app would have failed in November — only the models changed", and Why AI Lags at Design.

Codex vs. Claude Code#

The two are the wiki's reference harnesses, repeatedly compared. Loop Engineering's central structural claim is that both now ship the same five primitives (automations, worktrees, skills, connectors/plugins, sub-agents) under different names, so the same agent loop works in either — evidence for harness shrinkage. Where they diverge is institutional: Codex sits inside OpenAI's GPT-5 ecosystem and the Symphony/App-Server orchestration stack; Claude Code inside Anthropic's. The "harness engineering" framing (OpenAI, April 2026) is Codex's house philosophy for an agent-first workflow.

Connections#

OpenAI — maker; Codex is OpenAI's agent-tooling thread in this corpus
Claude Code — the Anthropic-side peer harness Codex is compared against (same five loop primitives, different ecosystem)
Symphony — OpenAI's open-source orchestrator that drives Codex from Linear
Codex App Server Protocol — Codex's headless JSON-RPC protocol
Conversation-to-Delegation Shift — the June 2026 usage study built on Codex telemetry; its adoption curve and token-share data
Agentic Work Systematization — Codex's skills/plugins are the systematization substrate that study measures
Parallel Agent Orchestration — Codex's threaded model is what enables the concurrency the study documents
Loop Engineering — Codex as one of the two tool surfaces that now ship all five loop primitives
Harness Shrinkage as Models Improve — Codex absorbing harness capability (skills, automations, worktrees) into named product primitives
Andrew Ambrosino — product & engineering lead for the Codex desktop app; the source for the app's history, usage, and general-knowledge-work pivot
Implementation Abundance Inverts Product Work — the product-process thesis Ambrosino draws from building Codex
Build for the Next Model — the Codex app as the case study: same shape, different-intelligence releases (Nov→Feb; Operator→Atlas→Codex)
Why AI Lags at Design — Ambrosino's design-capability read, developed while building the app's front end
Role Averaging, Not Role Elimination — the "role collapse" the Codex org saw more of than the rest of OpenAI

Sources#

The Shift to Agentic AI: Evidence from Codex — OpenAI, June 2026 (Codex usage across three populations)
OpenAI Codex lead on the new shape of product work — Lenny's Podcast, June 2026 (Ambrosino on the Codex desktop app, its usage, and its trajectory)
Also referenced in: An open-source spec for Codex orchestration: Symphony., Harness engineering: leveraging Codex in an agent-first world, Loop Engineering