Worktabs: one window for all your Claude Code worktrees

The developer's frustration started with running multiple Claude sessions in one editor: each assistant worked without knowing what the others had changed, producing conflicts and wasted cleanup time. Splitting work into git worktrees solved the collisions but multiplied windows, and on Windows there is no native tab grouping to contain them. Opening the editor itself also added friction, since reaching a repository meant navigating Explorer or typing commands, even with tools like ghq and fzf to narrow the list. The last straw was seeing an assistant sit idle in approval-waiting state in another window, with no way to know how long it had been there. Existing parallel-agent tools did not fit: some live in the terminal, some lack the editor integration of the VS Code extension, and some are macOS-only. Worktabs deliberately keeps the usual VS Code editor and Claude Code extension rather than building a new chat interface, so there is little new to learn, and it leaves the user's environment untouched so ordinary worktrees remain if the app is abandoned. It also stops short of sending instructions automatically: when creating a worktree from an issue, it only drafts the prompt in the input field. The trade-off is memory, at about 0.8GB per tab plus about 1GB for the app overall, though unused tabs can be suspended.