Worktree Coordination FAQs

Question 1

How do I see what other Claude instances are working on?

Accepted Answer

You can use the `/worktree-status` command to view a list of all active instances, their current branches, their assigned tasks, and the specific files they have locked.

Question 2

What happens if an instance crashes while holding a lock?

Accepted Answer

The skill includes a heartbeat mechanism. Every 30 seconds, instances update their status; if an instance hasn't checked in for 5 minutes, it is marked as stale and its locks are automatically released.

Question 3

Can I use this with the native Claude Code Agent Teams feature?

Accepted Answer

If you have Agent Teams enabled, that feature's native coordination is preferred. This skill is specifically designed for non-Teams worktree scenarios where you are running multiple independent Claude Code sessions.

Question 4

How does this skill prevent file conflicts between instances?

Accepted Answer

It uses a centralized registry to implement file-level locking. Before any write or edit operation, the skill checks the registry and blocks Claude if another instance currently holds the lock for that specific file.

Question 5

Does this require special git configuration?

Accepted Answer

It works with standard git worktrees. It simply requires a shared coordination directory (usually symlinked in .claude/coordination/) so all instances can read and write to the same registry file.

Worktree Coordination

Worktree Coordination

Key Features

Use Cases

Key Features

Use Cases