{"version":"2.1.285","anchor":"worktree-registration-request-handler-with-no-in-bundle-call","canonical_anchor":"worktree-registration-request-handler-with-no-in-bundle-call","heading":"Groundwork for registering git worktrees","tier":"internal","area":"Worktrees","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/worktree-registration-request-handler-with-no-in-bundle-call","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Groundwork for registering git worktrees\n\nClaude Code gained a handler that checks a repository and one to four worktree paths, with no known way to reach it yet\n\n**Unclear.** How this handler is reached is not established.\n\n**What**\n\nA git worktree is an extra working copy of the same repository in another folder. Claude Code now has a handler that takes a repository location and one to four worktree paths, checks the repository, and reports a result for each path, such as whether it was kept. Anything else it receives is rejected as not a worktree registration request.\n\n**Why**\n\nThis looks like a new way for another program to talk to Claude Code, but nothing you can use yet.\n\n- Area: Worktrees\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}