What the addon does
The addon installs or detects Hermes Agent, creates a CARAPACE mobile bridge, writes a bridge token, configures launchd or systemd, and exposes Hermes through its own runtime path.
The Hermes addon is standalone. You do not need OpenClaw on this machine to install CARAPACE Hermes support. If OpenClaw is also present, CARAPACE can pair both runtimes under one machine toggle while keeping their state separated.
curl -fsSL https://carapace.info/install-hermes-agent.sh | bash
The addon installs or detects Hermes Agent, creates a CARAPACE mobile bridge, writes a bridge token, configures launchd or systemd, and exposes Hermes through its own runtime path.
If OpenClaw is on the same host, the app shows one physical machine with an OpenClaw / Hermes toggle. If this is Hermes-only, the app pairs it as a Hermes runtime. Hermes gets its own chat history, projects, cron jobs, agents, and sessions.
CARAPACE passes image attachments to Hermes through the supported CLI path: hermes chat -q with --image. The bridge also stores image attachments in history so iOS can render them later.
The Linux addon writes a systemd user service and environment file with a robust PATH covering ~/.local/bin, npm global bins, Hermes venv bins, Homebrew, and system paths.
The Mac addon uses launchd and the same bridge asset. The Mac setup wizard can install OpenClaw, Hermes support only, or both, but Hermes remains opt-in.
Health should report the Hermes runtime, chat should answer, projects and cron should load, and image chat should understand an attached image. If not, rerun the addon and restart the bridge service.
curl -s http://127.0.0.1:18796/health
systemctl --user status carapace-hermes-mobile-bridge # macOS launchctl print gui/$(id -u)/com.carapace.hermes-mobile-bridge