wolfpack-tailnet-control

Wolfpack Session Control

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.

Fast path

A top-level project session:

wolfpack session create <project> --harness <pi|claude|codex|gemini|cursor> --prompt '<instruction>' --json

A child of the current agent (same harness by default; full-startup assignment):

# Pi child: resolve the role model explicitly; use the reviewer setting for review.
IMPLEMENTER_MODEL="${WOLFPACK_IMPLEMENTER_MODEL:-openai-codex/gpt-6.1-sol:high}"
REVIEWER_MODEL="${WOLFPACK_REVIEWER_MODEL:-openai-codex/gpt-6.1-sol:high}"
wolfpack agent spawn <project> --harness pi --name 200-implementation --model "$IMPLEMENTER_MODEL" --plan .plans/000-task.md --notify-parent --json
# --model requires a pi child, not a pi parent. Omit it for other child harnesses.
wolfpack agent spawn <project> --harness claude --name 200-review --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. Replace <project> with --project-dir <path> when the user selects an existing directory outside the configured projects root; never pass both selectors. The CLI resolves relative paths and the server validates/canonicalizes the directory. Both creation commands perform one server-owned request and pass startup instructions without inheriting parent transcript/context. --harness <pi|claude|codex|gemini|cursor> overrides the inherited child harness while preserving parent lineage; shell is not a child harness. --model is child-only and requires a Pi child; an explicit user/project model overrides the role environment/default.

Use --name <session> for child agents and choose a short meaningful issue/role slug, for example 200-implementation, 200-delivery-review, or auth-boundary-audit. Avoid generic *-sub-agent names when the task purpose is known; Wolfpack will allocate a numbered suffix if the requested name is already taken. 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.