Worktrees & Git
Check the original Host and folder before retrying a worktree operation. A failed or lost response can leave a real worktree or Thread behind. Inspect the project’s Worktrees view and Git state; do not delete a conversation to repair an unrelated folder problem.
If a folder moved, restore or repair its Git worktree registration. For an unfinished merge, rebase or cherry-pick, review local changes before continuing or aborting it. If a branch or folder name is already in use, inspect that existing work before choosing a different name.
Commit-message and PR-description generation use the Host’s utility model or configured default model. Check that channel, model and credentials, plus the selected staged files or PR commit range. An active conversation is not required. If an earlier request has an unknown outcome, inspect it before starting a new request.