Coding agents · in Codex (CLI + cloud)

Codex for Codex (CLI + cloud)

CLI for active work + Cloud for backlog PRs in the Codex (CLI + cloud) stack. Codex CLI handles the same role Claude Code does: terminal agent with file system access. Codex Cloud is the ChatGPT-bundled cloud lane that takes a task and opens a PR while you do something else. Use both: hands-on for the work you're thinking about, cloud for the cleanup tickets in the queue.

Updated 2026-05-05· 1 weeks ago

Codex· CLI for active work + Cloud for backlog PRsClaude· Cross-vendor diff review

Where Codex fits in the workflow

Hands-on with Codex CLI

`codex` in your repo. Same shape as Claude Code: scope, plan, implement, run tests.

Prompt · Plan-and-implement from a ticket (Codex CLI)

Plan first, then implement. Ask 1 to 2 clarifying questions before you start writing if anything is genuinely ambiguous.

Ticket / problem:
"""
{{paste ticket}}
"""

Constraints:
- Smallest viable diff.
- Match the existing code style. Read nearby files before introducing a new pattern.
- Run the project's test command. Don't report done if it fails.
- Treat AGENTS.md / CLAUDE.md / .cursorrules at the repo root as authoritative.

When done: print the file list, the test result, and a 2-line summary I can paste as the commit message.

3
Backlog tickets via Codex Cloud
From ChatGPT, hand off the ticket with the repo selected. Cloud reads the repo, plans, opens a draft PR, and pings you. Read the PR description first; reject and retry if scope drifted.
5
Bounce findings back to Codex
For CLI work: paste Claude's findings into the same Codex session. For Cloud PRs: kick the same task back via the Cloud `Address review feedback` action with the findings as the new prompt.