Under the hood
Fast-resume worktree checks now log a specific reason when they bail out instead of failing silently
What
When Claude Code tries to quickly resume an existing git worktree, it first checks the repository's status. If that status check fails or shows uncommitted changes, it now logs a specific diagnostic message, such as status failed (code N) or tree read dirty under filter-driver-off pins, instead of just quietly giving up. The path also now accounts for filter-driver arguments (git settings that affect how file content is transformed on checkout) when deciding how to proceed.
Why
Having a specific logged reason makes it much easier to figure out why a worktree resume was skipped, rather than it just silently falling back to a slower path.