project-session-manager

To manage isolated development environments, you can provision per-task git worktrees and tmux sessions. This ensures clean, reproducible setups across projects, preventing workspace interference while you work on multiple tasks in parallel.

Yes, you can launch Claude Code inside an active tmux session. This provides in-context guidance and code assistance directly during PR reviews, issue fixes, or feature development within the isolated worktree.

The best way to automate tmux session orchestration is using a deterministic workflow with a persistent session registry. It manages cloning, worktree creation, and Claude Code launch, tracking active sessions via lifecycle commands like list, attach, and kill.

You can track and manage active sessions using a lightweight registry with end-to-end lifecycle commands. Commands such as review, fix, feature, list, attach, kill, cleanup, and status allow you to monitor and control session metadata easily.

Yes, provisioning a dedicated git worktree per issue fix prevents baseline drift. By isolating each task in its own worktree and tmux session, you eliminate context switching and maintain a clean baseline across multiple repositories.