project-session-manager

You can manage isolated Git worktrees with tmux by automating the creation of linked worktree directories and tmux sessions, allowing parallel work across issues and features without conflicts. A local registry tracks these sessions for quick discovery and switching.

Handling multiple development environments for concurrent PR reviews is best done by creating per-project Git worktrees linked to separate tmux sessions. This isolates dependencies and branches, while per-worktree metadata enables quick switching between active reviews.

Yes, you need Git with worktree support and tmux installed to automate dev environments. Optional CLI tools for providers can enhance integration, but the core workflow relies on Git and tmux to create isolated sessions and maintain the local registry at ~/.psm.

Yes, you can use project aliases to switch between Git worktrees and tmux sessions quickly. The system maintains a local sessions registry and per-worktree metadata, enabling rapid discovery and navigation across your parallel development tasks.

A worktree registry helps with cleanup by maintaining per-worktree metadata at ~/.psm, allowing easy identification and removal of isolated Git worktrees and their associated tmux sessions once a parallel task, issue fix, or PR is complete.

Using Git worktrees instead of cloning multiple repos for parallel feature development shares a single object database, saving disk space. Linking these worktrees to tmux sessions provides lightweight, isolated environments that prevent branch conflicts.