Your first day with Codex
Seven steps, one small practice folder, and a result you can check yourself. Follow the desktop route first; no programming experience is required for the read-only exercise.
Product labels can change. The official pages checked on 16 September 2026 describe Codex inside the ChatGPT desktop app. If your installed version looks different, use the linked guide and match the task and folder, rather than guessing from an old screenshot.
Download the practice folder
Includes a small website and README, requirements, and verification instructions in all three languages. Keep this ZIP as your untouched reference.
Prepare your computer
Make a small, separate place to learn before giving an agent access to files.
Do this
- Use a desktop or laptop with a browser and an Internet connection. Check the installer page for support for your operating system; this guide does not assume a particular RAM amount or a paid plan.
- Download the practice ZIP above. On Windows, right-click it and choose Extract All. On macOS, double-click it. Move the extracted codex-practice folder into Documents.
- Keep the original ZIP. Open README.en.md, then open index.en.html in your browser. You do not need Node.js, Git, or a web server for this first exercise.
Before you continue
- You see “Hello, Codex!” and a contact section in your language. The working folder is extracted, not still inside the ZIP.
If this step does not work
If a page shows source code, use Open with and select a browser. If links point into a ZIP viewer, extract again into a new folder. Leave your original work and the reference ZIP untouched.
Install the desktop app
Open the official application that provides the Codex workspace.
Do this
- Open the official guide for your OS below and follow its download link. On Windows, use its Microsoft Store installer. On macOS, check that the listed processor type matches your Mac. Linux users should check the supported distributions in its guide.
- Finish the installer steps shown on your computer, then open the app from Start or Applications. If it is already installed, open that copy and check its available updates instead of installing several copies.
- Use the desktop route for this guide. The CLI and IDE extension are alternatives for later; do not install every interface just to finish this exercise.
Before you continue
- The official app opens to its sign-in or workspace screen. Download completion alone is not installation completion.
If this step does not work
For unsupported OS, blocked installation, or an organization restriction, record the exact error and OS version and follow the official guide or your administrator. Do not disable device protection to force an installation. You can still read the lessons while access is unresolved.
Official reference ↗ · 2026-09-16
Sign in and select Codex
Reach the coding workspace with the account you intend to use.
Do this
- Use the app’s sign-in flow and complete it in the browser if prompted. Return to the desktop app afterward. Do not enter passwords or API keys on this academy website.
- Check the account and, if shown, the organization workspace. In the current official guide, choose Codex from the ChatGPT selector for code-related tasks.
- If Codex is missing or access is denied, use the displayed account message and official access information. Plan availability and organization policies can change; this lesson does not promise access on every account.
Before you continue
- You can start a Codex task, and the account/workspace is the one you chose.
If this step does not work
If sign-in keeps looping, first confirm that the browser completed authentication and that the app is online. Record the exact message. Use official support for account restrictions; do not buy a plan based only on an old tutorial.
Official reference ↗ · 2026-09-16
Choose the practice folder
Make the selected local folder explicit before sending a request.
Do this
- In Projects, create or select a local project for codex-practice. The current guide uses the project menu → Edit project → Add folder to attach a folder. Attach the extracted codex-practice folder.
- Inspect the attached folder list. For this exercise, use only the practice folder; do not attach Documents itself or a business folder. If the project offers Make primary, ensure this practice folder is primary.
- Start a new Codex task from this local project. Compare its working folder with File Explorer or Finder. If you see a remote/cloud location instead, return to the local practice project.
Before you continue
- README.en.md, index.en.html, and styles.css exist in the selected folder. The local project and the folder containing these files match.
If this step does not work
A “file not found” response often means the folder or filename needs checking, not that the file should be recreated. Reopen the extracted folder and reattach the correct path. Do not ask Codex to invent the missing file.
Official reference ↗ · 2026-09-16
Send your first read-only request
Learn what Codex actually inspected before authorizing a change.
Do this
- Copy the request below into the Codex task. Keep the three filenames and the no-edit boundary. You may ask Codex to explain its answer in your language.
- Send it once and watch the reported actions. The required work is inspection. If it proposes installation, deletion, publishing, or an unrelated edit, stop that action and restate the boundary.
- Wait for the explanation, then keep the answer for comparison. A confident answer is not proof that the files were read.
Expected evidence, not a scripted answer
The answer names README.en.md, index.en.html, and styles.css; identifies the page heading “Hello, Codex!” and the #contact section; and reports no edits. Open the files yourself to confirm each statement. Different wording is fine.
Before you continue
- The answer identifies actual filenames and evidence from their contents, and does not claim to have changed the project.
If this step does not work
If the answer is vague, ask it to point to the exact heading and section ID in index.en.html. If it cannot read the file, return to the folder step instead of accepting a guessed answer.
Check the result yourself
Separate what the agent said from what you can observe.
Do this
- Open index.en.html in the browser. Confirm the main heading is Hello, Codex! Click Contact and confirm the contact section is reached.
- Read VERIFY.en.md. Compare each claim with the actual filename, heading, and contact ID. Mark your own result PASS, FAIL, or NOT CHECKED; do not copy a pass result from Codex without checking.
- To confirm no edits, extract the original ZIP to a different reference folder and compare the files you allowed Codex to read. A Git diff is also useful if you already have a baseline repository; Git is optional for this first task.
Before you continue
- You can point to the heading, the #contact section, and unchanged file contents. Record any check you could not run as NOT CHECKED.
If this step does not work
If you have no before-copy, you cannot prove “unchanged” from a verbal report alone. Keep the current folder, extract a fresh practice copy, and repeat the read-only exercise with a reference available.
Official reference ↗ · 2026-09-16
Recover when the result is wrong
Give a specific correction, preserve your work, and verify again.
Do this
- Write down expected versus observed behavior: for example, “Expected: the heading in index.en.html. Observed: the answer describes a different page.” Include the exact filename and error text.
- Ask for only the failed check to be repeated in the same practice folder. Keep the original boundary: inspect and explain, no edits.
- If an unintended edit happened, keep a copy of the current folder and compare it with the untouched ZIP. Recover only the affected practice file after identifying the change; do not use a command that discards every change.
- Repeat the verification checklist. Finish with three lines: what was checked, the result, and what remains unverified. Continue to the first-task lesson only when this small exercise is understood.
Before you continue
- The correction addresses the observed problem, the files remain in scope, and your verification record is honest about anything still unresolved.
If this step does not work
If the error persists, stop repeating the same prompt. Keep the error, OS, app version, and selected folder path for diagnosis. Never include passwords or tokens in a shared screenshot.
Official reference ↗ · 2026-09-16