Codex

Modern Codex combines GPT-5.6-class models with an agent loop tuned for software trajectories: plan, read, edit, execute, observe, repair. When you submit a task, the system analyses repository structure, READMEs, manifests, configs, representative sources, to infer stack and conventions. Visible plans let you redirect before expensive implementation begins. Execution occurs in a sandboxed environment seeded from your connected repo. The agent installs dependencies with your project's package manager, applies edits, and frequently runs tests or typechecks. Failures feed back into the model context so patches are grounded in real stderr, not vibes. Isolation improves security and reproducibility: each run starts clean rather than inheriting a developer's half-broken local state. Model choice shapes behaviour and cost. Sol leans into harder multi-hop reasoning and careful tool use for thorny bugs. Terra aims at balanced quality/latency for everyday agent work. Luna maximises throughput per dollar, especially salient after OpenAI's late-July price-performance push cutting Luna sharply and Terra meaningfully. Product surfaces may default differently by ChatGPT plan; power users should explicitly route volume work away from Sol when policy allows. Delivery usually ends in Git commits and a pull request with narrative of decisions. Code review features can consume the same credit pools as implementation tasks depending on plan rules, budget review automation alongside build automation. The July 2026 ChatGPT desktop rebuild placed this loop beside Chat and Work so professionals stop alt-tabbing between a chat client and a dedicated Codex binary. CLI and IDE extensions extend the same agent identity into terminals and editors for people who never leave those habitats. Limitations are structural. Sandboxes cannot magically reach air-gapped production. Ambiguous product goals still require humans. Benchmarks and demos overstate reliability on messy private monorepos with sparse tests. Governance, SSO, retention, training opt-outs, belongs in Business/Enterprise conversations before you connect the crown jewels. Competitors (Claude Code, Cursor Composer 2.5, Copilot agentic CLI, Muse Code) pressure OpenAI to keep shipping; evaluate quarterly, not annually. Operationally, successful teams treat Codex as a queueing system with SLAs. They define ticket shapes that are eligible for autonomy (clear inputs/outputs, local testability, no unresolved product questions) and shapes that are banned (security-sensitive auth changes without human design, speculative refactors, anything requiring production data). They also instrument outcomes: percentage of PRs merged without refinement, median time-to-first-review, and credit burn per merged change. Those metrics catch silent quality regressions when model defaults shift after GPT-5.6 updates. Security reviewers should map Codex to existing AI tool policies. Sandbox isolation reduces laptop malware risk but does not eliminate training, retention, or exfiltration questions for proprietary code. Business and Enterprise contracts, SSO, and retention controls matter before connecting private monorepos. Pair that with branch protection rules so agent pushes cannot skip required reviewers. On the desktop side, remember the July 2026 merge: training materials that still screenshot a separate Codex.app confuse new hires and create shadow IT installs of obsolete builds. Finally, keep a competitive calendar. Claude Code limit changes, Cursor Composer releases, Copilot agentic CLI updates, and Meta Muse Code's August 2026 launch all change the relative value of staying OpenAI-centric. Re-evaluate quarterly with the same golden-path tickets so comparisons stay apples-to-apples on GPT-5.6 Sol/Terra/Luna versus rival stacks. Query variants this page must answer in plain language: what is openai codex (async GPT-5.6 agent with sandboxes and PRs); codex app mac (use ChatGPT desktop Codex after the 2026-07-09 merge); codex pricing (ChatGPT plan ladder, not a separate SKU); codex vs claude code (async PR factory vs interactive terminal); codex vs cursor (ChatGPT sandbox agent vs IDE-native Composer 2.5); codex vs muse code (OpenAI vs Meta terminal/agent stacks launched into the same 2026 Mac conversation). Dealbreakers: no clear acceptance criteria, no tests, no GitHub permissions for PRs, and regulated code without Business/Enterprise review. If those are true, fix the repo and policy first. Operational metric that matters: percentage of Codex PRs merged without a refinement loop. If that number is low, write better tickets before buying Pro 20×. On Mac specifically, install or update the ChatGPT desktop app, open the Codex surface, connect GitHub with least privilege, and run one tiny task before connecting crown-jewel monorepos. Uninstall obsolete standalone Codex.app shortcuts from internal wikis so new hires do not chase a dead binary.