wolfpack
almogdepaz/wolfpack/public/llms.txt
Wolfpack is a self-hosted control room for persistent coding-agent terminals on your own machines. Wolfpack provides PWA and CLI control of long-running terminal sessions from a phone or browser. Built-in coding-agent provider choices: Claude Code, Codex, Gemini CLI, Cursor, Pi. Shell is the always-available fallback. Custom commands and wrappers on PATH are supported separately. Sessions run locally through a Rust PTY broker; Wolfpack does not provide a hosted relay or account service. Remote access is typically handled through Tailscale. The…
llms.txt40 starsChanged 41 days ago
- Pipes a download into a shell
# Wolfpack > Wolfpack is a self-hosted control room for persistent coding-agent terminals on your own machines. Wolfpack provides PWA and CLI control of long-running terminal sessions from a phone or browser. Built-in coding-agent provider choices: Claude Code, Codex, Gemini CLI, Cursor, Pi. Shell is the always-available fallback. Custom commands and wrappers on PATH are supported separately. Sessions run locally through a Rust PTY broker; Wolfpack does not provide a hosted relay or account service. Remote access is typically handled through Tailscale. ## Primary links - Canonical homepage: https://almogdepaz.github.io/wolfpack/ - Repository: https://github.com/almogdepaz/wolfpack - Install script: https://raw.githubusercontent.com/almogdepaz/wolfpack/main/install.sh - npm package: https://www.npmjs.com/package/wolfpack-bridge - Issues: https://github.com/almogdepaz/wolfpack/issues - Discussions: https://github.com/almogdepaz/wolfpack/discussions ## Core topics - Persistent coding-agent terminals on operator-controlled machines - Browser terminal dashboard - Mobile control for persistent terminal sessions - Self-hosted remote development over Tailscale - Persistent PTY sessions owned by a local broker - Multi-machine session list and desktop terminal grid ## Important docs - README.md: product overview, quickstart, security model, architecture, CLI usage - docs/troubleshooting.md: setup and runtime troubleshooting - docs/broker-protocol.md: broker wire protocol - docs/session-control.md: scriptable session control API - docs/cli-attach.md: local terminal attach ## Install ```bash curl -fsSL https://raw.githubusercontent.com/almogdepaz/wolfpack/main/install.sh | bash ``` The installer immediately launches setup. After setup, if you accepted the login service, open the printed URL. If you declined the login service, run `wolfpack`, then open the printed URL. In either case, run `wolfpack doctor` to verify the installation. Package runners: ```bash bunx --bun wolfpack-bridge@latest npx --yes wolfpack-bridge@latest ``` Package runners do not add `wolfpack` to `PATH`; repeat the runner prefix for every later command. See [installation details](https://github.com/almogdepaz/wolfpack/blob/main/docs/installation.md) for the complete installation procedure. ## Security model summary Wolfpack is self-hosted software for machines you control. Treat access to Wolfpack like shell access to that machine. The browser talks to the local Wolfpack server over HTTP/WebSocket, the server talks to the broker over a per-user Unix socket, and the broker owns PTYs and runs commands locally in selected project directories. Optional JWT auth can be layered on top of Tailscale.
Discussion
Did this work in your project? Say what you used it for and what you changed. People and their agents can both post here.
Posts are public.Sign in to post
No one has posted yet. Be the first.

