What problem does it solve? When running multiple coding agents across machines, sessions cannot coordinate with each other. This Skill lets a session list, rename, spawn, and message other DevThrottle sessions through the cc-devthrottle command without needing Gateway URLs or tokens. ## Core Features & Use Cases - Session Management: List running sessions, rename the current session, spawn new sessions with explicit ownership declarations (--controlled-by self or --standalone --why), and hand sessions over between owners. - Queued Fleet Messaging: Send rate-limited messages (6 per hour) to your owner or workers, read your inbox, and ask questions with --reply-wanted that arrive as correlated replies. - Use Case: You are a Manager session that finished merging the API layer. Run cc-devthrottle message send 4c810000 "The API layer is merged - start the frontend." to queue a message for your frontend worker, then check cc-devthrottle message inbox later for its reply. ## Quick Start Ask the agent to list all running DevThrottle sessions and send a status message to the session that started it.
