SELF-HOSTED CONTROL ROOM FOR CODING AGENTS

Your agents.
Your machines.
Your tailnet.

See which agent needs you, answer from anywhere, and keep every session alive. Wolfpack runs on machines you own and reaches them over your Tailscale network.

  • No account
  • No relay
  • Tailscale is the trust boundary
  • Rust PTY broker outlives the server
  • MIT
wolfpack · sessions LIVE
2 machines · 8 sessions · 2 need youdemo sessions
01 / NEEDS YOU

Know which agent
needs you.

Every session on every machine, sorted by what it needs from you. Waiting agents float to the top; filters narrow the list to Needs you, Working, Idle or Failed.

Needs-input banner above a terminal: Allow edit to src/server/routes.ts? with y, n, esc and Reply in terminal buttons
Needs input

Answer in one click

On desktop a banner shows the agent's question with y n esc and Reply in terminal. On the phone, the terminal and its keyboard are the reply surface.

Session cards with harness icons and each agent's last line, including a Pi session showing its model, context and cost
Working · Idle

Read the last line

Each card shows the agent's latest line and its harness icon, working or idle. Pi sessions add the model, context and cost from their footer.

A failed docs-site session with a Close button between a session that needs input and a working one
Failed

Clear what is finished

A failed session says so in red and offers Close. Every tier keeps the order you give it.

02 / FROM YOUR PHONE

The control room
in your pocket.

Install Wolfpack as a PWA from your tailnet URL. Tap the session that needs you, answer with the keyboard accessory, go back, and open an agent on another machine.

  • Automatic idle alertsNeeds input only by default; switch to After rendered activity becomes idle, or Disabled.
  • Quiet while children workAn idle alert waits while one of the session's child agents is still working. Needs input is never held back.
  • One enrollment, every machineAgents can notify their parent, and one phone enrollment covers every online machine.
api-gateway needs inputAllow edit to src/server/routes.ts?
Illustration
01 ANSWER
Wolfpack phone terminal with colorized agent output and the keyboard accessory: Enter, Esc, arrows, Control C and show keyboard
02 TERMINAL
Wolfpack phone session drawer with a parent session expanded to show its two child agents
03 DRAWER

Phone frames are rendered in a mobile browser emulator from demo sessions.

03 / THE CONTROL ROOM

Less SSH juggling.
More momentum.

A desktop workspace built around persistent terminals: switch instantly, resize live, tile sessions and follow agents that spawn agents.

Wolfpack dashboard: Needs you band, state filters with counts, and sessions grouped by machine

Dashboard

Sessions across machines with Needs you pinned first, filters with counts, ⌘K search and ⌘↑/↓ to move between sessions.

Wolfpack terminal view with the session sidebar and a needs-input banner

Terminal

Instant switching keeps recent terminals mounted. Take control or inspect when another viewer holds a session; reconnects show their state instead of failing silently.

Wolfpack grid with three demo sessions tiled side by side

Grid

Add sessions from the sidebar to tile up to six terminals, drag dividers to resize live, and move focus with ⌘⇧ and the arrow keys.

Wolfpack delegation grid: a parent agent and its two child agents, one reporting back

Delegation

An "N agents" chip nests child sessions under their parent. Open the parent to see the whole tree, and read child reports as they return.

Wolfpack terminal with an extension widget panel docked beside it showing a review checklist

Widgets

Extensions add context views you can dock left, right, bottom or full, pin or collapse, beside the terminal they belong to.

04 / EVERY MACHINE

One dashboard.
Every machine.

Wolfpack discovers other machines on your tailnet, verifies each peer before listing it, and groups sessions under their machine names. Offline and unreachable machines say so.

$ wolfpack --machine macbook list --json
Dashboard machine groups: Workstation with six sessions and MacBook with two
05 / AGENTS RUN AGENTS

Scriptable from
any agent.

The same CLI your agents call: create sessions, spawn children that report back, send input, wait for output and follow events, locally or on any machine with --machine.

$ wolfpack session create api-gateway --harness claude --plan .plans/200-review.md --json

create

Start a top-level agent session in a project with a plan file.

$ wolfpack agent spawn api-gateway --harness claude --name 200-security-review \
    --plan .plans/200-review.md --notify-parent --json
{ "ok": true, "session": "200-security-review", "sessionId": "…", "project": "api-gateway", "harness": "claude" }

spawn

Spawn a child of the current agent session; with --notify-parent it reports back when it is done.

$ wolfpack session send 200-security-review "focus on token expiry" --ensure-submitted
$ wolfpack session wait 200-security-review "Review complete" --timeout-ms 600000 --json

send + wait

Type into a session, confirm the submit, then block until its output contains a marker.

$ wolfpack events --kinds session.state,parent_notified
2026-10-26T09:04:12.418Z session.state 200-security-review working (program status)
2026-10-26T09:06:41.077Z parent_notified api-gateway seq=3 [201-load-test] p95 38 ms, 0 errors

events

Follow session, state, task and parent-notification events as they happen.

$ wolfpack agent inbox --since 2 --json

inbox

Read what child agents sent back to the current session.

Agents learn the commands from the bundled wolfpack-tailnet-control skill; Pi can opt into wolfpack-task-delegation. Session control reference

06 / BRING YOUR AGENTS

Bring the agents
you already use.

Claude CodeCodexGemini CLICursorPi

Shell is the always-available fallback. Add custom commands and wrappers in Settings → Agents, which also shows whether each one is ready.

07 / INSTALL ON YOUR MACHINE

Install Wolfpack.

Install leads into guided setup, which prints a local URL usable without Tailscale. Only after Tailscale sign-in and tailscale serve are verified does setup also print a private Tailnet HTTPS URL and QR code.

PERSISTENT CLI

Install once, run anywhere

Downloads verified native binaries, adds a stable command when possible, then opens setup.

curl -fsSL https://raw.githubusercontent.com/almogdepaz/wolfpack/main/install.sh | bash

Verify after setup: wolfpack doctor

NO PATH CHANGE / BUN

Run with Bunx

Use the latest package without installing a persistent global command.

bunx --bun wolfpack-bridge@latest

Verify: bunx --bun wolfpack-bridge@latest doctor

NO PATH CHANGE / NPM

Run with npm

Use the latest package without installing a persistent global command. Requires Node.js 22 or later.

npx --yes wolfpack-bridge@latest

Verify: npx --yes wolfpack-bridge@latest doctor

Bunx and npm make no persistent PATH change.

What the installer changes

The native installer downloads matching Wolfpack server and broker binaries from the latest GitHub release and verifies them with checksums-sha256.txt.

It installs the managed binaries under ~/.wolfpack/bin, attempts a best-effort /usr/local/bin/wolfpack symlink, then opens setup.

During setup, you choose the projects directory, port, optional Tailscale remote access, optional Pi integration when Pi is detected, and whether Wolfpack starts at login.

The package-runner options directly run the matching platform pair but make no persistent PATH change.

08 / YOUR INFRASTRUCTURE

Private by
construction.

Wolfpack is self-hosted software for machines you control. There is no Wolfpack account and no hosted relay: remote access travels through your Tailscale network, not through us.

  • Direct connectionsYour tailnet is the trust boundary, with optional JWT auth on top.
  • Persistent PTY sessionsA Rust broker owns the terminals, so agents survive closed tabs, dropped connections and server restarts.
  • Auditable surfaceMIT-licensed source, local config and an explicit service lifecycle.
Read the security model
THE FIRST REMOTE SESSION

Put the pack
to work.

Start local-only or connect through your tailnet, then reopen the same persistent session wherever you need it.

Wolfpack tour

An 86-second tour with demo sessions. Captions are burned into the video, and it has no audio.