1 · Interactive SSH
Full remote shell to Windows OpenSSH, Linux, Mac, Pi, NAS.
Daily path for most desk PCs: vw ssh <alias> or plain ssh user@host.
Rune
Interactive login, saved hosts, mesh, put and get, optional mosh, a health check, an on-device shell, and more than one session. For machines you control.
Connection forms · not SSH-only
One cockpit, several paths — pick the path that fits the job. Interactive login is the daily spine, but Rune also covers saved hosts, mesh, file transfer, optional mosh, health checks, on-device shell, and multi-session. All of it is for machines and logins you control, not a rented cloud desktop.
Full remote shell to Windows OpenSSH, Linux, Mac, Pi, NAS.
Daily path for most desk PCs: vw ssh <alias> or plain ssh user@host.
List aliases with vw hosts, connect with one name —
vw ssh hub (also pc once you set your mesh).
Mesh-aware: prefers home LAN, then Tailscale.
Phone + hosts on the same mesh so the same SSH login works from cellular or hotels — without port-forwarding your house to the open internet. How to set it up →
vw put phone → host · vw get host → phone · vw files help for options.
Same keys and host names as your shell sessions.
Optional smoother sessions over flaky Wi‑Fi / LTE when the remote runs mosh-server (Linux, Pi, or WSL). Plain Windows OpenSSH alone is not a mosh server — use SSH there, or mosh inside WSL/Linux.
vw doctor — tools, key, mesh, hub reachability in one shot.
vw control ping / sessions — quick link and tab checks from the shell.
Packages, git, local scripts, and vw war-room commands run on the phone
when you do not need a remote host at all.
Several shells at once (S1, S2, …). Close a tab cleanly and return to your first session. Prefer one session for daily use so the phone stays light.
Example flow:
unlock phone → open Void Walker → Rune →
vw hosts → vw ssh hub (or ssh you@lab-pc) →
you are on that host’s command line →
optional vw put / vw get for files →
run what you need → disconnect or leave the session up.