@shannholmberg
my entire Hermes Agent setup is controlled from one folder on a VPS I can manage it from my laptop or phone in under 10 seconds, spin up isolated agents per project, and never lose context here's the full setup: > bash command "ssh hermes" auto-connects to the VPS > session pinned in CMUX terminal for instant access > Claude Code session inside the ssh connection with full remote access > everything runs from a control station folder folder structure: vps-agents/ βββ README .md overview + how to use it βββ CLAUDE .md auto-loaded project context for Claude Code βββ agents/hermes-main/ β βββ inventory .md IP, hostname, where it runs, who owns it β βββ docker. md draft docker-compose + first-boot checklist β βββ runbook. md "it broke, what now" β 7 common scenarios β βββ env-map. md table of which keys live where (no values) β βββ backup. md GitHub backup flow + restore steps βββ shared/ βββ security. md VPS-wide hardening checklist βββ commands. md Docker / Hermes / UFW cheat sheet from this session I can spin up new docker-isolated agents per area and each one can have sub-profiles the whole stack is documented, backed up to GitHub, and accessible from anywhere