Shabadoo

shabadoo

A coordinator (**hub**), a per-host agent (**node**), and the installer for the launcher toolchain they drive. One binary, three roles.

Agents dial the coordinator and hold a command stream open; the coordinator merges every host's Claude sessions into one dashboard, routes writes to the agent that owns the pane, and records every action in an audit log. Because the agents dial out, only the coordinator needs to be reachable.

The dashboard lists every tmux session and window with live status (active pane, running command, cwd, idle time, auto-refreshing), and lets you **click a pane to select it**, **send text or slash-commands to it** (one-tap chips like `/remote-control`, plus a free-form box), **view its live transcript** (colored, `tail -f` style), **see what the Claude session in it is doing** (model, turns, tokens, tools — read from Claude's own record, not the screen), and **reopen / kill / open** windows. It is mobile-responsive; the chips make `/remote-control` a one-tap send from a phone.

It is also **the installer and source of truth for that toolchain**: the launcher is built in (`attach` / `win` / `boot`, once three shell scripts), and the portable `~/.claude` config (skills, settings) is compiled into the binary, so one copied file can set up a new machine offline.

**Security:** the deployment runs `--device-tokens` — every client (browser, CLI, phone) presents a credential it was enrolled with, and there is no anonymous access. That matters because a credential holder can read every project path, **read any session's transcript** (including file contents and anything ever pasted into a prompt) and **type keystrokes into any pane**, which run `claude --dangerously-skip-permissions`. Enrol anything that only needs to watch with `pair --scope read`, which cannot write at all. The coordinator is also tailnet-only. See [CLAUDE.md](CLAUDE.md) and [docs/shabadoo.md](docs/shabadoo.md).

Install

Prebuilt binaries and a con