agent-cli-tmux-supervision

Managing parallel Codex worktrees in tmux involves launching multiple agent-cli sessions and using a supervision skill to track progress, enforce review loops, and verify PR finalization across all active worktrees.

Tracking agent-cli progress across multiple worktrees is best handled by a supervision skill that polls each tmux session regularly, ensuring tasks complete without interruption and checking PR synchronization before finalization.

Yes, you need tmux to run this specific supervision setup. The Skill requires both agent-cli and tmux as dependencies to coordinate multiple worktrees, manage parallel sessions, and monitor progress effectively.

To set up review loops for agent-cli PRs, you use a supervision skill that implements current-context and fresh-context review protocols, ensuring code quality checks are completed before finalizing and syncing the pull request.

Yes, you can launch a new Codex worktree from a specific branch using the agent-cli command, specifying the source branch, agent type, tmux session name, and prompt file to initialize the supervised worktree.

A PR sync check for supervised worktrees confirms that all agent-cli tasks are complete and the pull request is correctly updated before finalization, preventing unsynchronized or incomplete code from being merged.