react-native-worktree

Switching Metro ports atomically reclaims inactive ports and safely redirects device connections to the active Metro server, ensuring concurrent React Native feature work does not collide on shared testing simulators.

Automatic port switching and worktree registration reclaim Metro ports when worktrees become inactive, preventing conflicts and ensuring continuous React Native development across multiple concurrent agents.

Yes, the coordination mechanism acquires per-platform mutex locks, allowing concurrent agents to test React Native features on iOS and Android simulators simultaneously without device conflicts.

Inactive worktree locks are released through heartbeat-based lock maintenance, which automatically refreshes active locks and cleanly releases them when a worktree becomes inactive during concurrent React Native testing.

You register a worktree by running an add command that automatically detects the bundle ID and platform from app.json or app.config.js files, then assigns the appropriate Metro port for concurrent React Native testing.

The primary limitation is that mutex coordination requires heartbeat maintenance to prevent stale locks, meaning inactive worktrees must properly signal release to avoid blocking other agents from accessing devices and Metro ports.