Topic
A Git feature allowing multiple working directories, each checked out to a different branch, to share one repository.
Anthropic's Windows app 2.31226.0.0 holds gated code giving each repo in a Claude Code session its own Git worktree, RuntimeWire found. Two feature gates keep the controls hidden, so the package shows the workflow's design but not when it ships.
Reality
OpenAI's Codex CLI refresh, builds 0.156.0 to 0.160.0, pitches /fork as a separate checkout, but its command reference says /fork clones only the chat. Two agents on one repo need a worktree session, started from the new agent command center.
Reality
Relipa's AI development workflow wraps a coding agent in six stages and fixes the tests before any code is written. Most of its published detail covers the workspace plumbing that runs before a model is ever called.
Reality
Andrew Pyle runs parallel coding agents in separate git worktrees cut from origin/main, at about a second and a few megabytes each. All the worktrees share the repository's one object store, so setup stays cheap and the remaining coordination happens in a single merge.
Reality
The desktop app creates a real git worktree for every task and launches a CLI agent inside it. The isolation is the same git command you already have. The product is the review loop built around it.
Reality
One developer's test on Claude Code 2.1.263 lost a clean worktree and its branch at /exit with no prompt. The cleanup routine he extracted only releases locks whose reason it wrote itself, so a lock set by hand holds.
Reality
Two coding agents in one working directory will commit over each other and leave you tracing diffs by hand. A worktree per session removes the collision. What's left after that is the real limit: how fast you can review.
Reality
One practitioner's teardown notes: shared authenticated sessions, half-redirected homes, hardlinks that deny being links, and a delete that blames permissions for something else.
Reality