Blog · Codex guide · Published

Codex Tutorial: Choose the Right Entry Point and Complete Your First Project Task

Tell apart the desktop, web cloud, command line, and editor entry points, sign in along the official path, provide project context, start with a small task that has a clear scope, then check the results.

When using Codex (OpenAI's coding assistant) for the first time, choose an entry point based on where you work: start local projects from the desktop app, and use a cloud environment for remote coding tasks. After signing in, provide the files or context the task requires, and begin with one small task that has a clear scope and results you can verify.

How do I choose between the web, command line, and editor entry points?

OpenAI's official quickstart lists the different entry points; choose according to how you work:

  • Desktop app: Suited to local projects; it can read and modify files in the folder you select.
  • Web cloud: Suited to remote coding work; you can select or create a Codex Cloud (cloud runtime environment).
  • Codex CLI (command line tool): Suited to developers who are used to working in a terminal.
  • Codex IDE extension (code editor extension): Suited to developers who want to stay inside their editor.

Just pick one entry point and complete the task. The instructions below focus on the desktop app; for installing the command line tool and the editor extension, follow the links on the official quickstart to the relevant pages.

After signing in, how do I start working on a local project?

Follow the official desktop workflow:

  1. From the download entry point on the quickstart page, choose the app for your operating system, install it, and open it.
  2. Sign in with your own ChatGPT account.
  3. From the ChatGPT dropdown menu, select Codex to enter the coding workspace.
  4. Open the project folder you want to work on, then describe the task.

When working on a local project, first confirm that you have opened the target folder, then ask Codex to answer based on the files inside it and to list the paths it cites. You can also add relevant files or context as the task requires; you do not need to make the entire project the scope of your first task.

I want to work on tasks on the web — how do I prepare a cloud environment?

In a new task, select Work in > Cloud, open Select environment, then choose Create environment.

Codex will inspect the repository and help prepare and test the environment setup. Once you confirm the setup is as expected, you publish the environment; after publishing, you can start and continue cloud tasks on the web, on mobile, or in the desktop app.

It is advisable to first check the target repository and the environment check results. If problems arise during preparation, resolve the environment setup first, then submit the coding task.

How should I write the first task?

The official guidance is to state the goal and add the files or context needed. In practice, you can structure your request into three parts: goal, scope, and deliverable.

Suppose you have just taken over an existing project. You could start like this:

Read the project documentation and related configuration, and explain how the project starts. List the startup entry point, the file paths this is based on, and any prerequisites I need to confirm. For now, only read — do not modify files; clearly mark anything you cannot confirm.

The acceptance criterion for this task is a startup explanation backed by files. If the answer is vague, keep asking for the relevant paths or configuration details, and only arrange modifications once the evidence is in place.

After receiving the answer, how do I judge whether the task is complete?

Open the files the answer cites and check whether the startup command, entry point, and prerequisites are consistent. If you find a contradiction, feed back the specific file and the point of contradiction, and ask it to re-check.

When you later need code changes, describe the behavior you want changed, the scope of modifications allowed, and the verification requirements, and ask it to distinguish between checks it has already run and parts not yet verified. That way you can judge whether the result meets the requirements and what additional verification is still needed.

If what is holding you back is plan support or usage limits, see Codex pricing and subscription plans.

FAQ

Which entry point should I choose the first time I use Codex?

Choose by where you work: use the desktop app for local projects, the web cloud for remote tasks, Codex CLI if you are used to a terminal, and the IDE extension if you want to stay in your editor. Just pick one entry point and complete the task.

How do I start working on a local project in the desktop app?

Download the app for your operating system from the official quickstart page, sign in with your ChatGPT account, select Codex from the menu, open the target project folder, then describe the task.

How should I phrase the first task?

Write it in three parts — goal, scope, and deliverable — and state clearly whether it may only read or may also modify. For example, first have it read the project documentation and configuration, explain how the project starts, list the file paths it relies on, and mark anything it cannot confirm.

How do I judge whether Codex's answer is trustworthy?

Open the files it cites and check them. If you find a contradiction, feed back the specific file and the point of contradiction and have it re-check; when you later request code changes, ask it to distinguish between checks it has performed and parts not yet verified.

Topic: Account and usage(All articles in this topic)

Ken|Operations Lead at TopupCat

Content is compiled by the TopupCat content team and published under the name of Ken, Operations Lead.View author profile

Related reading

Related products: ChatGPT Go · ChatGPT Plus · ChatGPT Pro · Top-up guide · FAQ · Self-service troubleshooting