Give your first safe task
Inspect a real practice folder, compare Codex’s explanation with the files, and prove that a read-only task left your work unchanged.
Complete the seven-step onboarding. Have the extracted codex-practice folder and the original ZIP ready. No Git, Node.js, or API key is required for this exercise.
WHAT · What you will learn
Your deliverable is a short file map with evidence: what each named file does, the exact page heading, and the contact section ID. You are practicing inspection, not building a new website.
A prompt is an instruction, not a technical security boundary. Check the selected folder and the tool actions as well as the final answer.
WHY · Why this matters
If Codex describes a file that is not in the folder, a later edit could target the wrong place. A small read-only task lets you catch a context error before it turns into a code change.
HOW · Follow the steps
- Extract the starter ZIP. Open its README in your language and the matching index HTML file; keep the ZIP as the before-copy.
- Select this exact folder as the local Codex project. Match the filenames with your file manager.
- Copy the request in the example. Send it once and let Codex inspect the three named files.
- Read the answer alongside the actual files. Confirm evidence before accepting the suggestion for the next exercise.
EXAMPLE · A worked example
Input: the downloaded starter, with index.en.html, styles.css and README.en.md. The HTML contains <h1>Hello, Codex!</h1>, a link to #contact and a section with id="contact".
A correct explanation identifies HTML as the content, CSS as the presentation, and README as the instructions. These are reference facts from the supplied files, not a fabricated transcript of a Codex run. Exact wording may differ.
Inspect only README.en.md, index.en.html, and styles.css in this practice folder.
1. List the files you actually read and explain their roles.
2. Quote the main heading and identify the contact section ID.
3. Suggest one small exercise, but do not perform it.
Do not create, edit, delete, install, or publish anything.
If a file is unavailable, name it and stop rather than inventing its contents.TRY IT · Do it yourself
- Ask a follow-up that names the back-to-top link and its target. Keep the no-edit boundary.
- Before reading the answer, find href="#top" and id="top" yourself. Then compare the explanation with your own observation.
VERIFY · Check the evidence
- File evidence: all three reported filenames exist in the selected folder. A missing file must be reported as missing.
- Content evidence: the exact heading is Hello, Codex! and the contact target is #contact. Check the HTML source, then the visible page.
- Change evidence: compare the three inspected files with a separate extraction of the original ZIP. A final “no changes” sentence is not a file comparison.
- Completion record: write what passed, what failed, and what you could not check. Stop if the selected folder or evidence is wrong.
COMMON ERRORS · Recognize the failure
- Opening the ZIP viewer instead of the extracted folder makes the working path confusing.
- Accepting a general website explanation even though the file names or heading are wrong.
- Allowing a file edit because Codex suggests an improvement during the read-only task.
FIX · Recover deliberately
- Wrong path: reselect the extracted practice folder and repeat only the file inspection.
- Unsupported claim: ask for the exact file and text that support it. If Codex cannot read them, record NOT CHECKED.
- Unexpected edit: preserve the current copy, compare with the ZIP, and restore only the affected practice file. Repeat the read-only task afterward.
NEXT · Continue when ready
You are ready when you can verify a file-based answer and preserve the original files. Next, reproduce one visible navigation bug before asking for a one-line fix.
Sources and scope
Independent practice content. Product guidance reviewed on 16 September 2026. Reference HTML and expected outcomes are distinguished from actual recorded runs.
OpenAI · Projects and chats ↗OpenAI · Quickstart ↗