project-session-manager

You can manage parallel git worktrees by orchestrating isolated development environments with tmux sessions and a central registry. This prevents cross-project contamination by registering each workspace atomically and enforcing safe, root-validated worktree deletion.

Yes, you can launch a Codex runtime per session. The workflow enforces Codex launches alongside tmux orchestration for each isolated git worktree, ensuring consistent tooling and execution across your parallel development tasks.

The best way to coordinate cleanup is using cross-provider integrations with GitHub and Jira. This Skill fetches PRs and issues to track active sessions in a central registry, enabling safe, root-validated worktree deletion to prevent accidental data loss.

Tmux session orchestration works by attaching a dedicated tmux session to each atomic git worktree registration. This isolates multi-repo workflows like PR reviews and feature development, tracked centrally to prevent cross-project contamination across parallel tasks.

You need a central registry to track active worktrees and tmux sessions. It coordinates atomic session registration, manages cross-provider GitHub and Jira integrations, and validates safe worktree deletion to prevent cross-project contamination and accidental data loss.