Menu
Create top-level Wolfpack sessions, spawn child agents, and inspect or control local/Tailscale sessions through the canonical CLI.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Optional Ralph skill context for agents/users who install it. Defines the structured response expectations and user-notification endpoint; Wolfpack does not runtime-inject this skill into prompts.
Context injected into interactive claude sessions via --append-system-prompt. Defines the plan-file header conventions the task extractor recognizes. Loaded by src/wolfpack-context.ts.
| name | wolfpack-tailnet-control |
| description | Create top-level Wolfpack sessions, spawn child agents, and inspect or control local/Tailscale sessions through the canonical CLI. |
Use the canonical CLI. Do not discover or reconstruct browser/private HTTP flows. Wolfpack uses its ordinary global API auth policy and adds no inter-session authorization layer.
A top-level project session:
wolfpack session create <project> --harness <pi|claude|codex|gemini|cursor> --prompt '<instruction>' --json
A same-harness child of the current agent:
wolfpack agent spawn <project> --plan .plans/000-task.md --notify-parent --json
wolfpack session open is only a deprecated child-spawn alias. Never use it for a top-level request.
Both creation commands perform one server-owned request and pass startup instructions without inheriting parent transcript/context.
Prefer --plan <file> for plan work: Wolfpack generates the compact handoff prompt and verifies the file exists without copying plan contents into the parent transcript. Use --prompt-file <file> for long bespoke instructions. Use raw --prompt only for one short prompt sentence. Do NOT paste repository policy, architecture context, or full plans into the launch command.
wolfpack list --json
wolfpack session status <session-or-id> --json
wolfpack session read <session-or-id> --json
wolfpack session send <session-or-id> '<text>' --json
wolfpack session wait <session-or-id> '<text>' --json
Treat session selectors as opaque handles. Prefer the stable sessionId returned by create/spawn/list/status. If the user already supplied an exact target, do not list first.
Read-only inspection is allowed when requested. Creation, sending input, killing, taking control, remote-host access, and notifications require explicit user intent for that action and target. Never scrape terminal/UI prose as protocol, bypass auth, guess tokens, or kill a mistaken session as cleanup without permission.
docs/session-control.mdREADME.mddocs/troubleshooting.mddocs/broker-protocol.mdskills/wolfpack-ralph/SKILL.md