Hermes Vpn

Good to know before installing

- a root-owned helper, installed out of band by the user through a narrow exact-path sudoers rule, is the only thing that reads the credentials and writes them to a root-only file (the agent names a country, never the key), and it pulls the gluetun image pinned by digest; the helper manages gluetun Docker containers, bringing exits up and down; the plugin registers a tool_execution middleware that holds browser_* calls when no verified exit is up (the kill switch, and optional cross-provider failover); it verifies exits by calling public IP-geolocation services (ipinfo, ifconfig.co, ip2location, cloudflare); credential entry is CLI-only, with no model tool for it -- `hermes vpn provider <name> --set` (interactive) or `--from-ref`, which resolves a WireGuard config from pass/gopass or a host file host-side and never returns it to the model; opening a .onion needs `hermes vpn allow-onion`, a terminal command a person runs (no model tool) that turns off Hermes's own internal-address check so onion names resolve and restarts Hermes, and the plugin never writes that setting itself; the active profile comes from the plugin context (ctx.profile_name), not a private core import.

From the plugin's catalog listing.