{"version":"2.1.321","anchor":"enterworktree-and-tmux-and-iterm2-backends-reworked","canonical_anchor":"enterworktree-and-tmux-and-iterm2-backends-reworked","heading":"Failed worktree creation now logs when Claude Code cannot return to your directory","tier":"internal","area":"Worktrees","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/enterworktree-and-tmux-and-iterm2-backends-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Failed worktree creation now logs when Claude Code cannot return to your directory\n\nIf creating a worktree fails and the session cannot go back to its directory, Claude Code now logs that, and handles such errors in one place\n\n**What**\n\nA worktree is a separate working copy of a git repository. Claude uses the `EnterWorktree` tool to create one and move the session into it. If creation fails, Claude Code already tried to put the session back in its original directory. It now logs a message when it cannot do that, and worktree creation errors go through one shared handler. The tool also records an extra folder location when it runs.\n\nThe parts of Claude Code that drive tmux and iTerm2 windows were also slimmed down.\n\n**Why**\n\nWhen worktree creation fails and leaves the session somewhere unexpected, there is now a record of it.\n\n- Area: Worktrees\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}