I built a private control room for coding agents running on my machines

AI coding agents are good at working unattended. The awkward part starts when they need input: the terminal is on another laptop, a workstation, or a cloud VM, and the work is spread across SSH windows and tmux panes.

I built Wolfpack to solve that specific problem.

Wolfpack is a self-hosted browser and mobile command center for Claude Code, Codex CLI, Gemini CLI, and shell sessions. It runs on the machines where the agents already run. There is no Wolfpack account, hosted relay, or prompt-storage service. Remote access normally goes directly over a private Tailscale network.

The important design choice is that sessions belong to a persistent Rust PTY broker rather than the web server. Restarting or redeploying the dashboard does not have to kill the agents doing the work.

The workflow

1. Install Wolfpack on a machine running your coding agents.
2. Connect the machines and phone to the same Tailscale tailnet.
3. Scan the private HTTPS QR code printed during setup.
4. Open the PWA and see sessions across your machines.
5. Respond when an agent needs input, then leave it working.

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

What it is not

Wolfpack is not another coding agent, cloud workspace, or hosted orchestration platform. It is the control room around agents that are already running under your control.

That also means it is intentionally opinionated: self-hosted, local-first, and connected through infrastructure you choose. The current tradeoff is that deployment security still needs deliberate configuration before exposing it beyond a trusted private network.

Try it

The README has the demo, setup walkthrough, supported platforms, and troubleshooting guide. Feedback on installation and the two-machine workflow is more useful than stars: those are the parts I am trying to make boring.