What problem does it solve? Managing multiple parallel Claude Code sessions across different projects is chaotic — sessions get lost, names clash, and there is no central point of control. This Skill turns one Claude session into a dedicated orchestrator that spawns, names, messages, and cleans up child Claude sessions running in tmux. ## Core Features & Use Cases - Child Session Spawning: Creates named tmux sessions running sandboxed Claude Code instances (with permission bypass flags) in any project directory, then verifies startup and enables remote control. - Session Management: Lists active Claude sessions, sends messages to named children via remote-control or tmux send-keys fallback, and kills sessions on explicit request. - Port Dashboard: Ensures the always-on port-dash dashboard is running at port 9999 so you can monitor services across sessions. - Use Case: Say "spin up yolo Claudes for my api and frontend repos" and the master session creates two named tmux sessions, boots a permission-bypassed Claude in each, enables remote control, and hands you the attach commands. ## Quick Start Ask the master session to spin up a new Claude session for your project directory, for example: "start a new claude session in ~/projects/my-app".
