wtp Git Worktrees

Based on satococoa's wtp workflow: https://dev.to/satococoa/wtp-a-better-git-worktree-cli-tool-4i8l

Use wtp for worktrees it manages. For T3 Code worktrees, use the app's workspace tools for creation and the completion workflow below for cleanup.

Worktree ownership

Before creating or finishing a worktree, inspect git worktree list --porcelain and the current app's workspace binding. Use wtp list to distinguish managed worktrees from external ones; a path under ~/.t3/worktrees/ is also a T3 hint.

• wtp-managed: follow the wtp workflow below.
• T3-created or otherwise unmanaged: remove directly with Git after the completion checks. Skip wtp remove, which cannot manage these worktrees.
• New T3 workspace: use the exposed app orchestration tools to bind the thread to its workspace. Creating a directory with wtp or Git, or changing the shell directory, does not update T3's thread binding. Use a handoff for the current thread and an explicitly bound launch when the user requests a separate thread.

Why use it