during execution
Direct terminal mirroring
ColliePWA streams raw agent terminal output with full ANSI color support, avoiding lossy transcripts or summaries. The mobile view matches your desktop terminal byte for byte.
A mobile interface for your terminal agents.
ColliePWA meets you where you already work, in the terminal multiplexer on your machine. Coding agents run in split panes and prompt for input. ColliePWA lists running instances, flags blocked sessions, and lets you respond from a phone.
- Multiplexer backend:
- Herdr
- tmux
- Zellij
Herdr is the primary supported backend in 1.0. tmux and zellij support is experimental. Details in Multiplexers
Static interface capture with mock sessions. The demo interface is non-interactive.
01/Demo
Interactive demo.
This is the production ColliePWA client. Agents, terminals, and responses use mock data replayed locally in your browser. Nothing runs on a server and no network traffic is sent.
- 01Select the blocked agent at the top of the list.
- 02Inspect the prompt. This mirrors raw terminal output directly.
- 03Tap a response to resume execution.
- 04Select Keys to access modifiers and navigation: Esc, Tab, arrows, and Ctrl.
02/Core architecture
Core primitives and 1.0 additions.
on input required
Single-tap input responses
Interactive permission prompts render as discrete action buttons. Input is validated against current terminal state before dispatch to prevent desynced submissions.
New in 1.0
03Localization support
Interface translations for English, German, Spanish, Korean, Japanese, and Chinese, configured in Settings. Only UI chrome is translated; agent terminal streams remain byte-exact.
04Explicit device authorization
collie pair generates an eight-character token with a ten-minute TTL and five-attempt limit. The client exchanges this for an auth token whose hash is stored by the bridge. Revoking a device drops its next request.
05Voice input transcription
Push-to-talk transcribes directly into the input composer. Supports OpenAI-compatible APIs, local whisper.cpp or parakeet.cpp instances, or existing Codex CLI credentials without separate keys. Requires HTTPS via tailscale serve or a reverse proxy.
06Web Push on state change
Optional Web Push delivers notifications when an agent blocks on input or finishes. Selecting a notification opens that agent. Transition filters and do-not-disturb periods are bridge-wide across every device. Requires HTTPS and collie push-keys.
07Git worktree workspaces
Herdr nests git worktrees directly under their parent repository checkout instead of creating top-level entries. Worktrees are tracked as native workspaces.
08Zen mode
An optional setting that adds a toggle to the pane menu to collapse all navigation and display only the terminal. Leaves a single floating button to exit.
Network topology
09Configurable transport gateway
ColliePWA binds strictly to localhost without public ingress. Transport to mobile devices can use the automated Tailscale configuration in collie start, WireGuard meshes, tunnels, or standard reverse proxies.
10Multi-host crew coordination
A crew is ColliePWA on every machine. Your phone reaches them all through the lead. Uploads, journals, audit logs, updates and failover are per machine, under tmux and zellij too. Herdr's saved machines stay in Herdr's own window. The crew is what your phone sees.
Additional features
- 11Unified process supervision
- Aggregates running agents by execution state, prioritizing blocked processes at the top of the interface.
- 12Full scrollback retention
- ColliePWA streams complete agent session logs, preserving historical scrollback beyond the current terminal viewport.
- 13Multi-session multiplexing
- Exposes all configured Herdr sessions from a single gateway, selectable from the top navigation bar.
03/Who it is for
For developers who run agents in a multiplexer and step away from the desk.
ColliePWA is for one operator with several coding agents running in terminal panes on one host. It does not replace the terminal. It lets you answer a waiting agent from a phone, then go back to what you were doing.
- Meets you where you already work
- It connects to the multiplexer you already run, Herdr, tmux, or zellij. No new session model and no wrapper around the agent. Herdr is the supported backend in 1.0. tmux and zellij are experimental.
- No app store, no cloud, no account
- A PWA served from your own machine over your tailnet. No store listing, no vendor account, and no cloud tier. The only outside services are the ones you switch on: the browser push service, and a cloud transcription endpoint if you pick one over a local engine. Add it to the home screen and it runs like an app.
- Built for the keyboard you do not have
- Special keys, arrows, and modifiers sit on a keypad. Your own quick replies and slash commands take one tap. The composer is a plain text field, so phone dictation works directly. Built-in voice input is available once you run
collie stt setupon an HTTPS origin. - Notifications when an agent needs input
- Optional Web Push alerts you when an agent blocks on input or finishes. Tapping the notification opens that pane. Requires HTTPS and
collie push-keys. - Several machines, one URL
- A crew puts every host behind one address, with a failover you authorize ahead of time and trigger from the browser. One confirm updates the whole crew from the same screen.
- MIT licensed. Come and contribute.
- The source is on GitHub under the MIT license. Bug reports from tmux and zellij setups are welcome, including reports of setups that work.
04/Architecture
Local execution model and security boundaries.
ColliePWA writes to your interactive terminal sessions with your current user permissions. Any client with network access to the port can read terminal output and execute arbitrary commands.
- Runs on the local agent host
- Directly mirrors local multiplexer sessions. Herdr is fully supported in 1.0; tmux and zellij backends are experimental. Operates without cloud backends, remote servers, or external accounts.
- Loopback-only binding
- It binds to loopback and never to 0.0.0.0. Exactly one hardened front door is published — tailscale serve, or a reverse proxy you configure. Never funnel.
- Host-level authentication
- Access control is handled at the network layer rather than through application logins. Any user on an authorized device has full shell access.
- Local system access boundary
- Multiplexer unix domain sockets enforce local filesystem permissions. ColliePWA's TCP port is accessible to other local users. Enforce isolation using ingress filters and COLLIE_TRUSTED_USER.
MIT licensed source. Review the security note for detailed access controls and trust boundaries.
05/Installation
Install via shell script or build from source.
ColliePWA runs next to your agents, on the machine that already has them. The script downloads a release for your platform and verifies it. Building from source needs git and Bun, and is the route for a machine the releases do not cover. Both end with collie on your PATH, and neither one starts anything.
$ curl -fsSL https://colliepwa.dev/install.sh | sh
A short POSIX sh installer. It skips sudo, starts no system services, and isolates files to ~/.local/share/collie and ~/.local/bin. It fetches the latest release, validates the published sha256 hash, writes the binary, and updates PATH. Requires curl, tar, and sha256 tools.
Served locally from this origin. Canonical source is located at scripts/install.sh in the repository. Inspect the script before running:
$ curl -fsSL https://raw.githubusercontent.com/AltanS/collie/main/scripts/install.sh | less$ curl -fsSL https://raw.githubusercontent.com/AltanS/collie/main/scripts/install.sh | sh
Run collie update to fetch, verify, and switch to newer releases. Previous versions remain cached for collie update --rollback. Source builds update git revisions directly without release rollback targets.
Sourced from scripts/install.sh at 2ded11d, 2026-08-31.
One step left: start it.
# one step left. It asks which multiplexer to mirror — herdr, tmux or# zellij — and writes your answer to ~/.config/collie/.env, creating it.$ collie start
Configuration is optional and lives in ~/.config/collie/.env, the file start creates. Set COLLIE_TRUSTED_USER there, and the port or the front door if the defaults do not fit.
Access the generated URL from your mobile device over your local network. Add to home screen for full viewport mode.
Requires private ingress. ColliePWA binds strictly to loopback interfaces. Tailscale is configured by default: collie start runs tailscale serve on your MagicDNS hostname. Custom reverse proxies, meshes, and SSH tunnels are documented in DEPLOYMENT.md. Single-user architecture only.