One Garp connection for Codex, Hermes and other MCP clients.
Hermes
Ask your Hermes agent to carry out this setup on its own machine. It can download the setup helper and use the key you already supplied, keeping it in the active profile’s secret storage. You do not need to edit YAML or construct authentication headers yourself.
If Garp is already added but cannot connect, have the agent run python3 garp-hermes.py connect. This repairs the connection using its saved key, backs up the profile and tests real MCP calls. For another profile, include --profile NAME. If no key has been saved yet, provide it once at the helper’s hidden prompt.
A missing or invalid key is a connection issue. Do not purchase access to fix it. The helper reports inactive access separately.
Use your existing Hermes installation and model. If local browser or desktop controls are missing, run this setup once on the computer that runs Hermes.
Download the local setup for Hermes
Open Terminal in the download folder and run:
python3 garp-hermes.py setup
Setup reuses your configured Garp key or asks for it at a hidden prompt. It verifies access, backs up the active Hermes profile, enables local controls and installs their Hermes-managed drivers. Your model stays selected.
A short read-only test checks whether your model can call Garp and drive the browser. It uses your selected model and its normal billing, if any. Add --skip-agent-test to skip the test.
Hermes uses its supported local browser profile mode. Add --fresh-browser for a fresh browser. Terminal and desktop/API sessions are configured by default; add --surface telegram for Telegram or --profile NAME for another Hermes profile.
Approve any macOS permissions reported by hermes computer-use doctor, then start a fresh Hermes chat. Recheck later with python3 garp-hermes.py check.