Codex CLI adds worktrees, joining Claude Code and Kilo Code

OpenAI tagged Codex CLI 0.154.0 on September 9 with experimental support for worktrees, reachable through a --worktree flag or a /worktree command. New or forked sessions can now run in their own checkout, with commands to browse and resume across them instead of juggling one working directory per task.

The release also adds a way to answer questions inline while Codex keeps working, without losing your main draft, and gives Windows sessions a shared background Codex server with daemon lifecycle commands.

None of this is new territory on its own. Kilo Code's JetBrains 7.1.6 added move-a-session-to-a-worktree on September 8. Claude Code shipped a parallel-checkout --worktree flag on September 9, the same day as Codex. Three tools, three teams, the same primitive.

That convergence says something about where the real work is. Git worktrees solve the isolation problem, running several agent sessions without them stepping on each other's file changes, and that part is basically settled. What's still open is the lifecycle around it: forking a session into a new worktree, moving one after the fact, resuming across several, rebasing the results back together. Codex's /worktree command and Kilo's move-to-worktree feature are both bets on making that lifecycle less manual.

If you're running more than one agent session against the same repo, worktrees are worth turning on regardless of which tool you use. The open question is whether any of these three converge on the same lifecycle commands too, or whether forking and rebasing stay tool-specific enough that switching agents means relearning your workflow.