Your First Codex Task: Organize Product Files Step by Step

Codex Beginner Path · Step 4 of 5

• Previous: Write a clear AI task brief — optional; you can still follow this guide directly
• Goal: start from opening Codex and complete one safe file-organization task.
• Estimated time: 10–20 minutes.

💡 This guide does not repeat installation. If you can open the desktop app, switch to Codex, and see the task input box, start with Step 1. You do not need to know prompt engineering or describe everything perfectly at once. In this guide, product files means product documents, specification files, and images.

Current app name · August 3, 2026

OpenAI has started integrating Codex into the new ChatGPT desktop app. Codex remains a separate view, and existing Codex workflows continue to work. The desktop icon may say ChatGPT or Codex. Open the app, then select Codex from the top-left menu if you are not already there. See OpenAI’s migration guide.

💡 Why this exercise? Organizing product files is common in international trade, but this practice task does not contact customers, change a business system, or spend money. That makes it suitable for a first real task.

What success looks like: the source copies remain unchanged, organized copies appear in 03-output, uncertain items are recorded for review, and Codex produces a file index plus a processing report. You can follow the numbered steps and paste the message blocks without memorizing them.

1. Prepare a Safe Practice Folder

Create a folder named Codex-Test, then add four subfolders. If folder creation is new to you: in Windows File Explorer, right-click an empty area and choose New → Folder; on macOS, choose File → New Folder in Finder.

Codex-Test/
├── 01-originals/
├── 02-to-process/
├── 03-output/
└── 04-needs-review/

• 01-originals: recoverable reference copies for you to compare;
• 02-to-process: the only input Codex may read and process in this exercise;
• 03-output: new or copied results created by Codex;
• 04-needs-review: a written record of items Codex cannot determine safely; keep the source files in 02-to-process instead of moving them.

Read the English steps, not the visible Chinese names

All screenshots in this article come from an earlier Chinese-language Windows reference run. They are visual examples, not a second set of instructions.

• The first screenshot shows Codex-Test-Preview; create Codex-Test instead.
• Folder mapping: 01-原始资料 = 01-originals, 02-待处理 = 02-to-process, 03-输出结果 = 03-output, and 04-待确认 = 04-needs-review.
• Other screenshots may show a different project name or an older folder boundary. Follow the numbered English steps and copyable prompts in this guide.
• On macOS, controls may appear in different positions, but the folder names, task boundaries, and approval rules are the same.

Place two to five test file copies in 01-originals, then copy two to five of them into 02-to-process. For example:

02-to-process/
├── A100-specs.txt
├── A100-front.jpg
└── B200-spec.md

No real material is required. You can create two to five TXT or Markdown files in 01-originals, add a few fictional product names, models, and specifications, then copy them into 02-to-process. The purpose is to learn the workflow, not to maximize volume or realism.

Do not practice on the only copy

Do not include an irreplaceable original, password, API key, contract, quotation, complete customer database, or private information. These four folders help you and the AI understand scope; they are not operating-system-level isolation. Your task instructions must still say that only 02-to-process may be processed.

2. Open Codex and Select This Folder

1. Open the ChatGPT desktop app, select Codex from the top-left menu if needed, and create a new task.
2. Find Select project or the current project name near the input box.
3. Select the Codex-Test root folder, not only 02-to-process.
4. For this first exercise, use the approval-first permission mode (Request approval in the tested interface).
5. Confirm that Codex-Test appears near the input box before continuing.

Use this image only to locate the controls. The visible project is not Codex-Test; confirm that your own task shows Codex-Test before continuing.

Do not select your whole computer

Do not select the entire Desktop, Downloads folder, system drive, home folder, or a large directory containing contracts and customer data. Use only this recoverable, non-sensitive practice folder.

If you cannot find the project selector or approval mode, follow the illustrated workspace guide, then return here. If your version uses different wording, choose the mode that asks before writing files, accessing folders outside the task, or using the internet.

Before Step 3, check only two things: the selected project is Codex-Test, and the permission mode is Request approval or an equivalent approval-first mode. If either is wrong, stop and fix it first.

3. Not Sure How to Describe the Task? Let Codex Ask You

The first blocker is often not a button. It is the question: What should I say to Codex?

A task brief is simply a short checklist of the goal, allowed folders, prohibited actions, sample size, and expected result. Codex can help you write it.

You do not need to write a long, perfect prompt. Start with a rough idea, then ask Codex to clarify it one question at a time.

3.1 Copy This as Your First Message

Paste this into the Codex task input box:

I want to organize a small set of product files,
but I do not know how to explain the task clearly.

For now, do not read or modify files, and do not run commands.
Ask me one simple question at a time, up to five questions.
Clarify the goal, file scope, prohibited actions, sample size,
and expected deliverables.

After the questions, turn my answers into a task brief.
Mark missing information as “Needs confirmation.”
Then stop and wait for my review.

The message has only two essential rules: clarify first and do not act yet. If Codex starts preparing to work instead of asking a question, respond:

Stop here. We are only discussing the task.
Do not read files, run commands, or modify anything.
Ask me the first clarification question.

You do not need technical language. Answer in your own words, for example:

I mainly want the files organized by product model so they are easier to upload to a website. Do not change the originals. Start with one sample batch containing only two or three files.

A beginner only needs to remember three phrases

1. Discuss first; do not act.
2. Read-only inventory is allowed.
3. You may act now, but create a small sample first.

These phrases separate discussion, inspection, and modification. Do not say “start,” “process everything,” or “take full control” before you intentionally move to the next stage.

3.2 Review the Task Brief Before Continuing

A polished task brief can still contain the wrong boundary. Check at least these six points:

• Goal: organize materials, not rewrite product specifications;
• Read scope: only 02-to-process;
• Write scope: only 03-output and 04-needs-review;
• Prohibited actions: no deleting, moving, overwriting, uploading, publishing, or sharing externally;
• Sample size: at most three, or the actual number available when fewer exist;
• Stop point: inventory first, propose a plan, and wait for approval before creating samples.

If any item is hard to understand, reply:

Rewrite this task brief in plain language.
Make it easy for a beginner to check line by line.
Each step should do only one thing.
Keep the folder names, prohibited actions,
approval points, and deliverables.
Keep unconfirmed information marked as “Needs confirmation.”
Do not add new assumptions.
Stop after rewriting the brief. Do not operate on files.

Even when the task brief is correct, do not approve a full batch. The next step grants permission only to inspect the specified input files.

Optional: When should I use a separate ChatGPT chat first?

Discussing directly in Codex is the shortest path. Use a separate ChatGPT chat first if you have not selected a workspace, do not want Codex to access local files yet, or only want help clarifying your thinking.

I want Codex to organize a small set of product files,
but I do not know how to describe the task.

Ask up to five simple questions, one at a time.
Clarify the goal, allowed materials, prohibited actions, sample size,
and deliverables.

After I answer, create a task brief that I can copy into Codex.
Mark missing information as “Needs confirmation.”
Do not invent details or assume that you can access my computer.

Copy only the final task instructions back into Codex. Do not paste passwords, API keys, customer data, or other sensitive information. Then continue with Step 4.

4. Allow a Read-Only Inventory

This is the second gate. A read-only inventory means listing and summarizing the specified files without changing them. Codex may now inspect only the specified input. Paste:

The task brief is correct. Read-only inventory is now allowed.

Inventory the files in `02-to-process`.

Do not read or modify `01-originals`.
For now, do not modify, move, rename, overwrite, or delete any file.

Report:
1. filename;
2. file type;
3. likely product model;
4. evidence for that conclusion;
5. anything that cannot be determined.

Separate direct facts, inferences based on filenames,
and items that need human confirmation.

If Codex asks for approval, approve only a clear read-only action

For this step, approve only an action that reads or lists files inside Codex-Test/02-to-process. Deny the request if it mentions writing, moving, renaming, overwriting, deleting, internet access, uploading, 01-originals, or any unrelated folder.

If the request is difficult to understand, deny it and reply:

Explain the requested action in plain language.
Name every folder it would access.
Tell me whether it would change any file.
Do not execute it. Wait for my approval.

Do not choose Always allow during this first exercise.

Expected result: Codex lists only the files that actually exist and separates facts, inferences, and unresolved items. No new file should appear yet.

Check the file count and product-model interpretation. Correct the inventory before moving on if you find an error.

Reference image only: this older run read one fictional file from 01-originals. Do not copy that path. For this tutorial, follow the prompt above and inventory only 02-to-process.

The AI did not invent extra files to match an example count. It separated the available information into:

• Facts: content directly supported by a file;
• Inferences: conclusions based on a filename or surrounding context;
• Needs review: items without enough evidence and therefore requiring a person.

Reporting the number of files that actually exist is more important than producing a list that merely looks complete.

5. Ask for an Organization Plan Before Codex Acts

Based on the inventory I have confirmed, design an organization plan.

Requirements:
- create folders by product model;
- leave source files unchanged;
- place organized results in `03-output`;
- if needed, create or update
  `04-needs-review/unresolved-items.md`
  for files whose model cannot be confirmed;
- do not move or copy those unresolved source files;
- include a `README.md` in each product folder;
  this is a plain-text note explaining what the folder contains
  and what still needs confirmation;
- create `product-material-index.md` directly inside `03-output`,
  not inside a product subfolder.

Show the proposed directory structure first.
Do not execute the plan yet.

You should see a structure similar to:

03-output/
├── A100/
│   ├── README.md
│   └── material copies
├── B200/
│   ├── README.md
│   └── material copies
└── product-material-index.md

This image shows the expected form of a plan, not proof that no file was written. Review the directory structure and rules, then check 03-output yourself before approving execution.

6. Approve a Sample of Up to Three Files

Do not approve the full batch immediately after the plan looks reasonable.

The plan is approved for one sample batch.
Process up to 3 files whose product model can be confirmed.

If fewer than 3 files can be confirmed,
process only the actual confirmable number.
Do not invent files or expand the scope just to reach 3.

Requirements:
- copy only; do not move source files;
- do not overwrite existing files;
- do not process files whose model cannot be confirmed;
- stop after the sample;
- list every file created or copied in this run.

Use this image only as an example of a one-file sample and a reported skip. Confirm the actual source and output files in File Explorer or Finder.

Only one source file could be confirmed in this reference test, so the exercise used a controlled one-file adaptation. “At most three” is a ceiling, not a quota. If an output with the same name already exists, skip it and report the conflict instead of overwriting the previous result.

Reference-test limitations

These screenshots came from an already-installed Windows 11 environment using CC Switch with the third-party Laifa AI configuration. You do not need CC Switch or Laifa AI to follow the folder-and-approval method in this guide.

The screenshots demonstrate only this narrow method: specified one-file read-only inventory → plan without execution → controlled one-file sample → no overwrite of an existing output. They do not verify the current 02-to-process-only boundary, official ChatGPT sign-in, macOS behavior, a full batch, or real business data.

7. Review the Sample Yourself

Open the output folder and check:

• whether the product model is correct;
• whether images are in the correct folder;
• whether every source file still exists;
• whether each README contains only information supported by the source files;
• whether a filename-based inference was presented as an official specification;
• whether the AI exceeded the sample size you approved;
• whether anything outside the task scope was changed.

If you find a problem, copy and adjust this correction message:

The sample needs these corrections:

1. Copy images without renaming them.
2. In README files, list filenames only; do not infer product uses.
3. List files with an unknown model in
   `04-needs-review/unresolved-items.md`.
   Do not move the source files.

Restate the revised rules first.
Then create a revised sample using filenames with `-revised`.
Do not overwrite or delete the original sample.
List every new file when finished.

8. Process the Remaining Files and Create Delivery Records

After the sample passes, send the message below. It covers both possible situations:

• files remain in 02-to-process: process them under the same rules;
• the sample already covered every file: do not process anything again; create only the final records.

The sample is approved.

First check whether `02-to-process` contains unprocessed files.

If files remain, process them using the same rules.
Continue to follow these boundaries:
- do not delete or move source files;
- do not replace source files or existing copied product files;
- writes are allowed only inside `03-output/` and `04-needs-review/`:
  - create product folders and copy confirmed files into them;
  - create or update the `README.md` inside each product folder;
  - create or update the material index, and create the processing
    report (both at the root of `03-output/`);
  - unresolved items go only into
    `04-needs-review/unresolved-items.md`;
- do not create, modify, or delete anything outside these two folders;
- if a copied filename already exists, skip it and report the conflict;
- do not move or copy unresolved source files;
- do not send, upload, or publish anything externally.

If no files remain, do not copy files again
or create extra content to reach a target number.

In either case, finish by:
1. updating `03-output/product-material-index.md`;
2. creating `03-output/processing-report.md`;
   if it already exists, create `processing-report-2.md`
   instead of replacing it;
3. listing files read, copied, and created,
   plus unresolved, failed, and skipped items;
4. stopping and waiting for my review.

Open both files and confirm that they describe the actual results, not a plan or an assumption.

Then check the actual folders in File Explorer or Finder. The final structure should look roughly like this:

Codex-Test/
├── 01-originals/                  unchanged
├── 02-to-process/                 unchanged
├── 03-output/
│   ├── product-model folders/
│   ├── product-material-index.md
│   └── processing-report.md         or a numbered version
└── 04-needs-review/
    └── unresolved-items.md         only if review is needed

9. The Transferable Skill Is Not File Organization

The method behind this exercise applies to many other jobs:

Prepare copies
→ discuss and clarify
→ inventory first
→ propose a plan
→ create a small sample
→ review it yourself
→ expand the scope only after approval
→ produce a delivery record

Use the same sequence later for Word documents, PDFs, spreadsheets, website content, or other AI tools.

10. Completion Check

• Codex-Test was selected, and the first exercise required approval before changes rather than granting full access.
• The task was discussed and the task brief was reviewed before file access; if a separate ChatGPT chat was used, only non-sensitive task instructions were copied.
• Only test material or recoverable copies were used.
• The inventory request named only 02-to-process, and I denied any approval request involving 01-originals or an unrelated path.
• Inventory came before any batch organization.
• The proposed directory structure was reviewed first.
• One sample batch contained no more than three confirmable files; if fewer existed, only the actual number was used.
• Remaining files were processed only after human review; if none remained, no files were processed again and only the final records were created.
• Source files were not deleted, moved, or overwritten.
• Any unresolved items were listed in 04-needs-review/unresolved-items.md, and their source files were not moved.
• The final index and processing report were created and reviewed.

11. Next Step

Codex may have finished executing, but “execution finished” does not mean “the result is correct.” The final lesson covers formal review and a safe closeout.

👉 Continue to Step 5: review results and finish safely →

← Return to Step 3: write a task brief