Start with a small, reversible project
Codex can inspect a project, edit files and run development tools. This is different from asking a chatbot for code you must copy yourself. Pick a disposable project or make a backup first. Our suggested first session is deliberately modest: explain the files, change one piece of text, then show the difference. A successful installation is not evidence that every proposed edit is correct.
Choose your interface
- Prefer buttons and a visible project view? Start at the official Codex app page and choose the download offered for your computer.
- Already use a code editor? Follow the editor-extension link in the official Codex repository.
- Comfortable with a terminal? Use the CLI instructions below. You do not need all three interfaces.
Install the terminal version
Use only the command for your operating system. These official commands download and run an installer; review the linked source before executing them.
Windows PowerShell
powershell -ExecutionPolicy ByPass -c "irm https://chatgpt.com/codex/install.ps1 | iex"
The execution-policy flag applies to this installer process, not a recommendation to disable system protections globally.
macOS or Linux terminal
curl -fsSL https://chatgpt.com/codex/install.sh | sh
The official repository also offers npm, Homebrew and direct platform binaries. Choose one installation method so future updates are straightforward.
Sign in without confusing the bill
Open a terminal in your chosen project folder and run codex. Select ChatGPT sign-in to use eligible subscription access. API-key sign-in instead uses your API account's billing and policies. Check the active method with codex login status. These are distinct choices, not two names for the same allowance. See OpenAI's authentication guide and our model-access guide.
Your first task
- Create a backup or Git checkpoint.
- Ask: “Explain this project's purpose and main files. Do not change anything yet.”
- Check that the explanation names real files in the folder you intended.
- Then request one tiny change, such as correcting a heading, and ask it to show the diff and relevant checks.
- Read the changed lines and open the result yourself before keeping it.
Expected result: a response grounded in your actual project, followed by an inspectable change. “Done” without a diff or a working result is not enough. The CLI guide explains the task loop and permissions controls.
If something goes wrong
If the command is not found, reopen the terminal after installation and confirm you used the correct platform instructions. If sign-in succeeds but a request fails, check the selected account, workspace and billing method before reinstalling. If an edit touches unrelated files, stop and restore your checkpoint rather than stacking more fixes on top.
Keep credentials out of project folders, screenshots and support messages. Start with narrow permissions; do not enable broad unattended access merely to silence a prompt. Update through the installation method you chose, then repeat the small first-task check. This guide is documentation-checked, not a claim that every operating-system path was installed and tested by The Butler.