Anthropic's Windows app carries gated code that gives each added repo its own Claude Code worktree

The setup starts in the environment editor. Each added folder there gets "Select branch" and "Use worktree" controls ^[6]. A worktree is an extra working directory linked to a repository, so a developer can work on another branch without cloning it a second time ^[5]. In a local session, RuntimeWire's reading of the package has the app run three steps at start ^[8]:

1. The native manager checks the repository details and workspace trust. 2. It asks the worktree manager to create or reuse a worktree, then waits for checkout. 3. The client maps each added folder to its working copy.

I would look hardest at step two. "Create or reuse" means a folder can be attached to a worktree that existed before the session started ^[8]. RuntimeWire also describes an in-place fallback and says developers will still need to check which folders actually received isolated working copies ^[16]. The report does not say what triggers the fallback. In a multi-repo team I would keep a hand-built worktree script until that is documented, because the script records where every copy lives.

The per-repository split for commits is the right design. A shared Claude session does not merge the underlying Git histories into one project, and the code directs commits and pull requests repository by repository ^[20]. In RuntimeWire's example, a developer changing a web application and its separate API adds both folders and picks a worktree for each ^[21]. That change comes out as two branches and two pull requests from one session ^[22]. The bundled instructions show intent only. RuntimeWire notes that static inspection does not establish how Claude behaves in a live session ^[10].

Three conditions control whether anyone sees the controls: a session-presets gate, a separate worktree gate, and the app advertising support ^[14]. RuntimeWire did not change those gates, enroll a production account or start the application ^{[14] [3]}. Its comparison covered Windows x64 only ^[13]. What the package does establish is that the feature is implemented in this build ^[1].

Anthropic's desktop documentation already describes worktrees for local sessions and multiple repositories in cloud sessions ^[17]. David Iya's October 7th guide covers using '/add-dir' to bring another folder into a session ^[18]. Luis Mori Guerra's March 18th guide walks through preparing worktrees across repositories by hand ^[19]. The new Windows code adds per-folder worktree setup to the editor and session start for local and SSH work. RuntimeWire says that could remove some of the manual preparation ^[2].