Codex made parallel agent work feel normal

Codex made parallel agent work feel like a normal engineering move.

The useful change was not merely that a model could write code. Multiple runs could live in separate sandboxes instead of one overloaded thread. The user starts to act less like someone chatting with one assistant and more like someone dispatching bounded jobs.

A single thread is a poor container for unrelated work. It accumulates stale context, keeps side quests alive, and forces one stream of supervision. Engineering is already parallel: a test runs while a fix is investigated, documentation moves while a bug is isolated, and a speculative branch can be discarded without damaging the main task.

Isolation is what makes parallelism useful. Each run should own its workspace, branch or worktree, logs, diff, and command history. A collision should be visible before merge:

agent a:
  task: fix markdown lint in three posts
  workspace: worktree-a
  allowed: src/content/blog

agent b:
  task: investigate RSS build failure
  workspace: worktree-b
  allowed: src/pages, src/lib

The task slice matters more than the agent count. Five vague assignments produce five vague diffs. Better units have distinct outputs:

• report repeated phrases in the archive
• rewrite one post while preserving frontmatter
• verify Markdown and build checks
• inspect RSS output for malformed excerpts

Parallel work moves the bottleneck to review. That is fine, but the product has to make review cheap: changed files, commands run, checks passed, assumptions, and conflicts. Without those surfaces, parallelism is a pile of output.

Overlap can be useful when it is intentional. One run can make the minimal fix while another traces the deeper cause or writes a test. Label the experiment and keep speculative work away from the mainline until it is reviewed.

The merge step is the truth. A local pass can still conflict with another accepted diff, stale a documentation change, or rely on a different dependency state. Final checks belong on the combined result.

Codex made parallel agent work feel normal because it matched software’s existing shape: bounded jobs, isolated workspaces, diffs, review, and an integration check.