remote shell client
Your terminal,
anywhere
clawee attaches a live shell on any of your machines and keeps it. Sessions survive disconnects, reboots, and network roams — pick one back up exactly where you left it, from any device.
Install
One command. Signed installer.
The installer is fetched over TLS and verified before anything runs. clawee needs burrowee and a paired gateway — see requirements.
$ curl -fsSL https://release.clawee.org/clawee/install.sh | sh
Hosting sessions on a box? Install the daemon too:
release.clawee.org/claweed/install.sh — full steps in the
docs.
How it works
clawee rides the burrowee transport.
clawee is the client. It speaks to your local burrowee daemon, which carries the connection through a relay and gateway to claweed — the session broker on the remote box.
Why clawee
Sessions that stay put
Detach, lose Wi-Fi, reboot your laptop — the remote shell keeps running. clawee -r resumes the last one.
Many machines, one client
Pair several gateways and switch between them — clawee work, or press g in the picker. Sessions stay grouped per gateway.
Device-key auth
Every stream authenticates with your device key; new devices knock and are approved. The private key never has to touch disk (ssh-agent).