devthrottle-sessions

Manage and message DevThrottle coding agent sessions across machines via the cc-devthrottle CLI.

96|11|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/thefrederiksen/devthrottle --skill devthrottle-sessions-thefrederiksen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devthrottle-sessions
Source: https://github.com/thefrederiksen/devthrottle/tree/main/plugins/devthrottle/skills/devthrottle-sessions
Command: npx skills add https://github.com/thefrederiksen/devthrottle --skill devthrottle-sessions-thefrederiksen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple coding agents run in parallel across machines, they cannot see or coordinate with each other. This Skill lets a session discover, name, message, spawn, and close other DevThrottle sessions attached to the same gateway. ## Core Features & Use Cases - Session discovery and naming: List every session across attached computers, inspect this session's identity with whoami, and rename sessions so parallel work stays distinguishable. - Queued inter-session messaging: Send rate-limited messages to parent or child sessions, read the inbox, and request replies with --reply-wanted without interrupting running work. - Session lifecycle control: Spawn new sessions with explicit ownership (--controlled-by self or --standalone --why) and flag finished sessions for graceful removal with session done. - Use Case: A coordinator session spawns a test-runner session on another machine, asks it which database schema is loaded via a reply-wanted message, reads the answer from its inbox, and flags the worker for removal when done. ## Quick Start Ask the agent to list all running DevThrottle sessions and send a message to one of them using cc-devthrottle.

Frequently Asked Questions about devthrottle-sessions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send a message to another coding agent session?▼

Use `cc-devthrottle message send <target> "text"`, where the target is a session id prefix or exact display name. Messages queue rather than interrupt, and you can only message the session that started you or sessions you started.

How do I list all running DevThrottle sessions?▼

Run `cc-devthrottle session list` to see every session across every computer attached to the same gateway. Use `cc-devthrottle session whoami` to see the current session's own id, name, machine, and repository.

Why does cc-devthrottle say CC_GATEWAY_URL is unset?▼

That error means the shell is not running inside a DevThrottle-launched session. Sessions launched by DevThrottle carry the gateway address and credential in their environment automatically, so no manual configuration exists.

What are the messaging limits between agent sessions?▼

The gateway allows at most six messages per hour, one message to the same recipient every ten minutes, and drops identical unread messages. Sessions can only message their parent or children, never siblings, and fleet-wide broadcasts require a human grant.

How do I spawn a new agent session on another machine?▼

Run `cc-devthrottle session spawn /path/to/repo` with either `--controlled-by self` or `--standalone --why "reason"`, plus `--name` or `--purpose`. Add `--machine other-computer` to target a different attached machine.