
GitHub Copilot
Alternative option
Your AI pair programmer — code completions and chat in real time.
Inspect, edit, and run code from the terminal, then hand longer tasks to the cloud
OpenAI Codex is a coding agent that works in the terminal, IDE, cloud, and ChatGPT apps. It inspects repositories, makes edits, runs commands, reviews changes, and opens pull requests, with local CLI, editor integration, and long-running cloud tasks under one account.
Updated
2026-10-21
Platforms
Windows / macOS / Linux / Web / iOS
Freemium
Freemium: the official pricing docs list a $0 Free plan for quick coding tasks, Go at $8 per month, Plus at $20 per month with Codex on web, CLI, IDE, and iOS, and Pro plans from $100 per month. An API key works in the CLI, SDK, and IDE extension without cloud features and is billed at API token prices; confirm current limits and regional availability on the official pricing page.
* Pricing is for reference only; see the official site for current pricing.
Explore a repository, plan a change, edit files, and run local tools while inspecting commands and diffs as they appear.
Each cloud task gets its own workspace, so longer work can continue while you review results and open a pull request later.
Bring open files and selections into the prompt, review edits in place, and connect local or remote MCP servers from the CLI.
Run Codex non-interactively in repeatable workflows, pipelines, and automated checks.
Keep exploration, edits, command runs, and reviews in one CLI loop, with codex exec for scripts and CI.
Start cloud tasks from repositories, then review diffs and open pull requests from web, mobile, or desktop.
Use open files and selections as context and review focused diffs beside the code.
Quick start
Start in the terminal on a real repository and ask it to explain one file's role first, so you see how it reads context before letting it edit anything.
Hand a small, well-scoped change to the CLI and review the diff, then send the same kind of task to a cloud task to compare quality and turnaround.
Once the pattern is stable, wire codex exec into a script or CI step so repetitive chores run without you in the loop.
Pro tip
The useful split is local for exploration, cloud for duration. Keep exploratory work and anything touching uncommitted changes in the terminal; move long, self-contained tasks to the cloud so they keep running while your machine sleeps. Never point automated codex exec jobs at an unprotected branch: give it a dedicated branch and require review, because the failure mode is a silent wrong commit rather than an error.
If this tool is not the right fit, explore these alternatives