Create and manage git worktrees for parallel coding sessions with zero dead time. Use when blocked on tests, builds, wanting to work on multiple branches, context switching, or exploring multiple approaches simultaneously.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Zero dead time. While one session runs tests, work on something else.
Use when waiting on tests, long builds, exploring approaches, or needing to review and develop simultaneously.
Claude Code:
claude --worktree # or claude -w (auto-creates isolated worktree)
Cursor / Any editor:
git worktree add ../project-feat feature-branch
# Open the new worktree folder in a second editor window
Both approaches create an isolated working copy where changes don't interfere with your main session.
These features are Claude Code-specific (skip if using Cursor):
claude -w auto-creates and cleans up worktreesisolation: worktree in agent frontmatterCtrl+F kills all background agents (two-press confirmation)Ctrl+B sends a task to backgroundgit worktree listgit worktree list
git worktree add ../project-feat feature-branch
git worktree add ../project-fix bugfix-branch
git worktree add ../project-exp -b experiment
git worktree remove ../project-feat
git worktree prune
Terminal 1: ~/project → Main work
Terminal 2: ~/project-feat → Feature development
Terminal 3: ~/project-fix → Bug fixes
Each worktree runs its own AI session independently.
| Scenario | Action |
|---|---|
| Tests running (2+ min) | Start new feature in worktree |
| Long build | Debug issue in parallel |
| Exploring approaches | Compare 2-3 simultaneously |
| Review + new work | Reviewer in one, dev in other |
| Waiting on CI | Start next task in worktree |
git -C ../project-feat statusgit worktree prune).No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Coordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team sizing, task decomposition, and when to use teams vs sub-agents vs worktrees.
The English summary is being prepared. Showing the original description.
Auto-configure quality gates, hooks, and settings for a new project. Detects project type and sets up appropriate tooling. Use when onboarding a new codebase.
The English summary is being prepared. Showing the original description.
Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern.
The English summary is being prepared. Showing the original description.
Capture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never leaks file paths or line numbers into the issue. Use when the user reports a bug conversationally, runs a QA pass, or says "file an issue", "log this as a bug", "capture this".
The English summary is being prepared. Showing the original description.
Smart context compaction with state preservation. Saves critical files, task progress, and working state before compaction, restores after. Use before manual compact or when auto-compact triggers.
The English summary is being prepared. Showing the original description.
Master the four operations of context engineering — Write, Select, Compress, Isolate. Manage token budgets, compaction strategies, and context partitioning to keep AI sessions sharp and efficient.
The English summary is being prepared. Showing the original description.