Codex for Beginners: Understand the Workspace, Conversation, File Changes, and Command Results

Start using Codex with a read-only exercise that helps you distinguish the workspace, conversation, actual file changes, and command results.

The easiest mistake to make when you first open Codex is to send one instruction and wait for it to “finish.” A more useful first skill is learning to see what it can access, what it changed, and what actions it actually performed.

You do not need to be a programmer to begin. Think of Codex as an assistant that can read material, propose changes, and show its work inside a defined workspace. Before writing a clever instruction, learn to recognize four parts of that process.

1. Workspace: what can it access for this task?

OpenAI's desktop-app guidance lets you begin from a conversation, project, or folder. For a beginner, a folder is more than a location on your computer. It is the material boundary for the task.

For your first exercise, create a small practice folder with one or two public or self-written text files. Do not use an entire work drive, client records, or a critical production project as your first workspace.

2. Conversation: you are explaining a goal, not only issuing commands

The conversation is where you describe the purpose, provide context, inspect a first result, and point out problems. Your first message does not need to look like code. Try:

First, list the files in this folder.
Do not modify anything yet.
In three points, explain what each file appears to be for and what you still need to know.

This asks Codex to read and explain before editing. After you inspect its response, you decide whether the next step should include a change.

3. Files: separate “read” from “changed”

Mentioning a file in the conversation does not mean Codex changed it. When it proposes or completes an edit, do not rely on a final sentence that says the task is done. Find the changed-file list and inspect whether each difference belongs to the task. If nothing changed, you should be able to verify that this was a read-only pass.

You do not need to understand every line on day one, but you should be able to ask:

4. Command results: an action happened, but correctness is not proven

Codex may read files, run commands, or execute checks. A command is simply an instruction to the computer, such as listing files or running a test. Its result tells you what the command reported. It is not an automatic certificate that the final work is correct.

When a result appears, ask two questions: what command ran, and did it succeed, fail, or merely print information? If a check passed, ask what that check proves—and what it does not prove.

Practice: create your first Codex observation note

Create a disposable practice folder and add one or two non-sensitive text files, such as a fictional event description. Then run one read-only exercise:

Read the files in this folder without modifying them.
Tell me which files you read, then summarize the content in three points.
Finally, state whether you changed any files or ran any other commands.

Do not inspect only the written answer. Look at the files and activity shown in the workspace, then fill in:

Folder opened for this task:
Files in the folder:
What I asked Codex to do first:
Files it actually read:
File changes: none / yes, file names:
Command results: none / yes, command:
What I still do not understand:

Acceptance check

You have completed the exercise when you can distinguish three things with visible evidence: what Codex said in the conversation, which files actually changed, and which commands actually ran. “No file changes” and “no additional commands” are valid results. The goal is to know where the evidence lives.

You are no longer only waiting for an AI answer; you are observing a work process. The next lesson explains how to choose the folder boundary, approval behavior, and network access without opening more scope than the task requires.

Official references

The product capabilities above are based on OpenAI's official documentation. Screens, labels, and available features may change by platform or version. The four observation points and exercise are Aaron's beginner teaching method.