Bewinxed/cawco

Caw&Co (CawCo in the product) is the agent canvas for any work, anywhere, in any harness: self-hosted, for one operator managing their own machines. Its browser dashboard shows which sessions need attention across machines and projects, so you can approve permissions, redirect work, or stop a session without opening every terminal. A daemon runs on each machine and connects to your hub.
## Install
Run this on the machine that will host your hub:
sh
curl -fsSL https://cawco.dev/install.sh | sh
The installer sets up the hub, dashboard, machine daemon, and sessiond process keeper as per-user services. It installs Bun and Node.js if missing, clones this repository into ~/.cawco/app, installs dependencies, and builds the dashboard. Linux requires systemd; macOS requires Apple's command-line tools and a logged-in desktop session.
On Linux, the installer uses administrator access to install missing prerequisite packages (git, curl, unzip, bash, tar, grep, or coreutils) through the system package manager. It also enables lingering for your user when needed, so the services keep running after logout. It prints the administrator commands before running them. If it can't obtain the required access, it stops and tells you what an administrator needs to run. Bun, Node.js, the checkout, and the service definitions stay under your account.
On macOS, missing command-line tools or other prerequisites stop installation with instructions to install them and rerun the installer.
## After install
Open the dashboard at , the URL the installer prints. That address is the dashboard on every computer running cawco: the hub machine serves it itself, and every other machine's agent carries it to the hub. Previews there run in their own process on Chrome, Edge and Brave. From a device without cawco, open the hub machine's name or address on the same port, such as . The root opens the Fleet board. Check that the connection is live and your machine is online.
On a tailnet, turn on HTTPS Certificates on Tailscale's DNS page, and give your user Tailscale's certificate once with sudo tailscale set --operator=$USER on the hub machine. The hub then serves the dashboard and every preview at https:// . .ts.net: on its tailnet address, so every device on the tailnet opens a secure context. The LAN address, cawco.local and localhost keep plain http on the same ports; the plain tailnet IP stops answering. Until both steps are done, Caw's Needs you shows the next one.
Add a project from the projects rail: name it, choose a machine, and pick its directory. Open the project and start a session with an instruction, or start empty. Review the machine, harness, model, permission mode, rules, and tools before starting. The session's transcript opens as it starts; when it needs permission, read the request and approve or deny it there.
## What it works with
CawCo runs Claude Code, OpenCode, and pi sessions. Claude sessions use the Claude Code installed on each machine, the claude on the daemon's PATH; CawCo ships none of its own. Install it with curl -fsSL https://claude.ai/install.sh | bash (Claude Code setup). Keep the hub on your own trusted network or tailnet. Never expose it publicly or port-forward it. CawCo has no sign-in of its own: anyone who can reach the hub can operate the fleet.