Codex IDE extension
For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending
.mdto the page URL.
Build with the context already in your editor
Work with Codex beside your code. Bring open files and selections into the prompt, review edits in place, and hand off longer work without breaking your flow.
Illustration: Interactive Codex IDE extension beside a code editor
Start here
Why use Codex IDE extension
- Use the context already open: Reference open files, selected code, and recent chats directly from the composer. Codex starts with the code you are already looking at, so you spend less time restating the problem.
- Review changes beside your code: Read the summary, inspect a focused diff, and follow up in the same chat. Keep only the changes you want while the source and rationale stay visible together.
- Delegate when the task grows: Keep quick iterations local, or connect Codex web when a task needs more time and room. Return to a reviewable result from the same editor workflow.
Getting started
Get started in your IDE.
Install or enable Codex, sign in, and start a chat with the context already open in your editor.
1. Install or enable Codex
Choose your IDE. VS Code and compatible editors use the Codex extension; Xcode and JetBrains IDEs provide their own integrations.
2. Open Codex
VS Code, Cursor, or Windsurf: choose the Codex icon. If it is not visible, open the Command Palette and run Codex: Open Codex Sidebar.
Xcode: open the coding assistant, start a new chat, and choose Codex as the agent.
JetBrains IDEs: open AI Chat and select Codex.
3. Start your first chat
Open a project and ask Codex to explain the codebase, make a focused change, or help you debug an issue. Create Git checkpoints before and after a task so you can revert changes.
Next steps
See what Codex can do in your IDE
Stay close to the code while Codex explains, edits, reviews, and delegates.
- Use the context already open: Add an open file, a selection, or a recent chat to the composer, then ask Codex to explain or edit the code with that context already attached.
- Review changes beside your code: Review a concise summary and the changed lines without an extra navigation pane. Inspect the two affected files, keep the edits you want, and ask for a follow-up from the same view.
- Delegate when the task gets bigger: Choose local work for fast, hands-on iteration, or connect Codex web to delegate a longer task. The chat stays available when you return to review the result.
Use Codex IDE extension when…
- You are making focused edits: Keep the relevant files and Codex in the same view.
- You are learning unfamiliar code: Ask about the files and symbols already open in the editor.
- You want to review changes in place: Inspect and apply edits alongside the source.
- You want to delegate a larger task: Start cloud work from the IDE and return to the result.