Tasks through to review

Codex

From a task to a reviewable change.

Codex can inspect a repository, edit code, and run development tools. Local worktrees and cloud environments give separate tasks room to progress in parallel.

OpenAI’s official Codex repository page screenshot
Screenshot of OpenAI’s official Codex repository. The product homepage could not be captured; this is an official source page.Official repository ↗

Meet the tool

Codex at a glance

Use Codex for a concrete engineering outcome: trace an unfamiliar module, implement a feature, or investigate a failing check. The CLI works with local files and the tools installed on your machine.

Independent tasks can use Git worktrees, while cloud tasks run in configured environments. Review the resulting diff and checks, then request a follow-up or move the work into your normal delivery process.

Quick facts · official documentation
AspectWhat to expectEvidence
Local workInspect, edit, and run code using Codex CLIOfficial guide ↗
Cloud workCoding tasks in configured, isolated environmentsOfficial guide ↗
Project guidanceRepository instructions in AGENTS.mdOfficial guide ↗

What it helps you do

Features & uses

Work with the actual project

The CLI can read files, edit code, and run local commands, keeping implementation and verification in the same task.

Give parallel work its own checkout

Git worktrees provide separate working copies for independent tasks, so each can develop without editing the same files.

Review a clear scope

Ask for a review of a branch or uncommitted changes. Codex returns prioritized findings without changing the working tree.

Inside the workflow

Codex in practice

A closer look from the official resources. Open the image to inspect it at full size.

Codex CLI splash
The Codex CLI splash image published in OpenAI’s official repository.Official source ↗

Start here

Getting started

  1. 1

    Define the outcome and context

    Choose the project and describe the expected behavior. Put repository conventions and commands in AGENTS.md.

  2. 2

    Choose where the task runs

    Use the local project for installed tools, a worktree for an independent change, or a configured cloud environment.

  3. 3

    Inspect the result together

    Read the diff and check output, ask for follow-up changes, and run a focused review before handing off the result.

VibeAtlas editorial guidance

Is Codex a good fit?

A suggested evaluation, based on the documented workflow.

Choose an outcome you can inspect in the repository

Try a small feature with an explicit acceptance condition, such as exporting a filtered table to CSV. Give Codex the relevant project and ask it to implement and verify the behavior. Read the diff and reported checks, then use a follow-up to resolve any edge cases.

When comparing local and cloud work, include environment setup in the evaluation. A cloud task needs its own dependencies and configuration; a successful local command does not establish that the cloud environment can run it.

Questions before you start

Frequently asked questions

What can Codex do with a local repository?

The CLI can inspect files, make edits, and run tools installed on the local machine. It supports interactive work and repeatable command-line workflows. Describe an observable result and review both the changes and the commands used to check them.

Read the official explanation
How is cloud work different from local work?

Cloud tasks run in dedicated environments configured for a connected repository. Dependencies, tools, variables, and setup steps must be available there. Local files and installed programs are not automatically transferred into the cloud environment.

Read the official explanation
How can separate tasks avoid editing the same checkout?

Git worktrees give tasks separate working directories within a repository. They are useful for independent changes, but each checkout still needs the setup required by the project. Review and integrate the changes through your normal Git workflow.

Read the official explanation
Where do I keep the project's instructions?

Use AGENTS.md to record conventions, useful commands, and repository-specific guidance. Keep the file accurate as the project evolves. Instructions supply context; the final diff and verification results remain the evidence for whether a task succeeded.

Read the official explanation

Made with this tool

Real projects6

These projects are part of the current public VibeAtlas collection.

Explore all projects

Resources

Sources

Summarized from these official resources. Check the website for current features and plans.

Guide updated

Explore more tools