Skip to content

Codex Web Parallel Feature Development — Shipping Multiple PRs Solo

Codex CLI Complete Guide

Treating Codex Web parallel development as a deliberate workflow lets a single builder ship multiple PRs a day without drowning in manual reviews. This guide maps the “branch planning → Codex Web tasks → auto review → merge” loop so you can orchestrate Codex Web parallel development with confidence.

Target Audience

  • Target: intermediate solo builders who already use Codex CLI/Web and care about speed over ceremony.
  • Goal: keep three or more feature branches in ...

Terminology and conventions

  • Codex Web: the chatgpt.com/codex cloud environment; every task spawns an isolated container.
  • Codex CLI: the codex command-line tool. Options such as --profile follow the DEV guide.
  • Codex task: a single execution unit issued from Codex Web or CLI. This article assumes one branch per task.

End-to-end workflow map

flowchart TD
    A[Backlog / TodoWrite] -->|feature/login| B[Codex Web Task 1]
    A -->|feature/dashboard| C[Codex Web Task 2]
    A -->|feature/api| D[Codex Web Task 3]
    B --> E[Draft PR #101]
    C --> F[Draft PR #102]
    D --> G[Draft PR #103]
    E & F & G --> H[Codex GitHub App Auto Review]
    H --> I[Human final check]
    I --> J[Merge & Release Notes]

Why this map matters

① One branch per task keeps ownership clean and avoids overlapping diffs.

② Tasks run in isolated containers, so the work continues even if you close the browser tab.

③ GitHub auto reviews let you reserve human focus for the final call.

Step 1 — Plan branches and dependencies

  1. Use TodoWrite or Issues to split your roadmap into three to five items and rank them.
  2. Group features that touch the same files, then decide how many you can safely run in parallel.
  3. Add a short “Definition of Done” per branch so you can paste the same block into Codex prompts.

Suggested format

feature/login-form
  - DoD: Supabase auth UI + `npm run test:auth`
feature/atlas-sync
  - DoD: MCP webhook sync + `pytest sync`

Step 2 — Run Codex Web tasks in parallel

2.1 Launch cloud tasks

  • Visit chatgpt.com/codex, connect your GitHub repo, start a cloud task, and target the branch name.
  • Open with a prompt that states branch, Definition of Done, required tooling/env vars, and the directory scope the agent may touch.
  • Each cloud task continues in the background and usually ends with a draft PR plus a summary comment.

Prompt skeleton

Context: feature/login-form (branch already pushed)
Goal: Implement Supabase auth + UI polish, run npm run test:auth
Deliverable: Draft PR with summary + checklist
Scope: docs/generative-ai/chatgpt/**

2.2 Keep local work in sync

  • When you need instant tweaks, run codex --profile dev "<prompt>" on the terminal (available in Codex CLI v0.50+ per the DEV guide) and keep the change set scoped.
  • Before mixing local edits back into the cloud task, run git pull --rebase origin feature/<name> so both contexts share the same base.

About the sample commands

Options such as --profile dev/quick are part of Codex CLI v0.50.0 and later. Double-check with codex --help if your environment is on an older release.

Step 3 — Blend auto review and human decisions

  • Install the Codex GitHub App and enable “review on PR creation.” Even draft PRs receive comments automatically.
  • Extend your PR template with sections for “tests executed,” “open questions,” and “Codex rerun trigger” so it is clear when the agent should try again.
What the Codex auto review checks
  • Lint/test logs run inside the task, including repro steps for failures.
  • Dangerous commands in the diff (rm -rf /, secret exposure, etc.) and their risk score.
  • Dependency mismatches such as forgetting to update package-lock.json, with patch suggestions.
  • During human review focus on narrative fit, naming, and UX wording; use a comment like @codex rerun review if you want the agent to revisit the patch.

Step 4 — Merge and retro

  1. gh pr checkout locally, run a smoke test, and merge from the CLI or GitHub UI.
  2. Use the Codex Web “Summarize PR” action (or codex summarize --pr <ID> if you are on CLI 0.53.0+) and copy the output into your changelog or TodoWrite log.
  3. Capture which branch pairs conflicted, then adjust the next cycle’s grouping rules accordingly.

Common pitfalls and mitigations

When conflicts keep happening

  • Are multiple branches touching the same config file? Group them or extract that change into a dedicated task.
  • Does every Codex task receive a scope hint like Scope: docs/generative-ai/... only?
  • Are you syncing with the latest main before starting each task? Run git pull --rebase origin main (or an equivalent workflow) first.
  • Auto review cannot judge UX copy. Record a 30-second screen share for yourself before releasing to catch layout or tone issues.
  • Reconfirm that Codex commits comply with signing/CLA requirements if your repo enforces them.

Topics to explore next

  • Using git rerere templates to tame repetitive conflict resolutions.
  • Turning Codex Web task prompts into JSON snippets that sync with TodoWrite.
  • Comparing throughput when splitting responsibilities between Claude Code and Codex Web.

Related content

References