OpenAI Codex
Coding agent that works inside a sandboxed repository, writes patches and runs tests, then returns a diff for review.
Quick facts
| Pricing | Premium |
|---|---|
| Free tier | Limited — included in some paid plans, with usage caps |
| Platforms | Web, CLI, code host integrations |
| Developer | OpenAI |
| Website | https://openai.com/codex/ |
What OpenAI Codex is
OpenAI Codex is a coding agent rather than an editor. It runs tasks in a sandbox with access to a repository: you describe a change, and it reads the code, writes patches, runs tests and returns a diff or a pull request. It is available through a web interface, a CLI and integrations with code hosts, and can work on several tasks in parallel. The design assumes a developer reviews the result rather than watching every step, which suits well-scoped changes — a bug fix, a refactor, a test suite — more than exploratory design work. Because it executes code in an isolated environment, dependency and setup problems surface early. The limits are context and judgement: large codebases need clear instructions about where to look, and generated changes still require review before merge. Tasks can be queued and reviewed as a list rather than one at a time, which changes how a small team splits work.
Best for
- Well-scoped fixes and refactors handed off and reviewed later
- Writing tests against existing behaviour
- Running several independent tasks in parallel
Not ideal for
- Exploratory design work with no clear target
- Repositories where the agent cannot build or run tests
Pros
- Runs tests before returning a diff
- Parallel tasks shorten a backlog
- Works from web, CLI and code hosts
Cons
- Needs precise scoping to be reliable
- Large codebases require guidance on where to look
- Usage limits bind during heavy periods
Pricing in detail
Codex usage is included in some OpenAI paid plans with a monthly allowance, and heavier use is metered or billed through API pricing. There is no separate per-seat product for every tier, so the effective cost depends on which plan you already hold and how many tasks you run. Because each task can involve many model calls, a handful of large refactors consumes more than a long chat session.