Codex can be used in repositories that are organized with git worktrees, but the safest answer is that worktree behavior depends on how the user launches and manages each Codex session. Do not claim a universal Codex-native worktree system unless the current official Codex documentation says so.
For parallel agent work, the real question is not just whether a tool can run in a worktree. It is whether the product helps separate tasks, preserve context, show changes clearly, and prevent agents from interfering with one another.
That is where Verdent has a cleaner story. Verdent's Workspace Isolation is built around git worktrees, with each workspace separated by directory, branch checkout, file state, and staging area. A Codex user can manually create isolation, but Verdent turns that pattern into a visible workflow for parallel agents. The practical benefit is less coordination overhead and a clearer review path before changes reach the main branch.
