How to Connect Remote Hermes or OpenClaw Runtimes to BenAgent
Configure BenAgent to talk to a Hermes or OpenClaw runtime running on another machine while keeping private transport, tool locality, and endpoint exposure clear.
BenAgent can use a runtime that is not running on the same Mac. The important rule is ownership: BenAgent is only the macOS surface. Hermes or OpenClaw still owns tools, files, sessions, network access, and model execution on the machine where the runtime runs.
Start local before going remote
- Hermes local default: http://127.0.0.1:8642 plus /v1/chat/completions.
- OpenClaw local default: http://127.0.0.1:18789 plus /v1/chat/completions.
- BenAgent sends a provider-scoped Bearer token only when you configure one in Settings; otherwise it sends no Authorization header.
- A remote URL should be introduced only after the local runtime answers a safe test message.
Hermes remote checklist
Enable the Hermes API server
On the remote host, enable the OpenAI-compatible API server. For a remote boundary, configure API_SERVER_KEY and save the same Hermes Bearer token in BenAgent Settings. Restart the gateway after changing the environment file.
API_SERVER_ENABLED=true
GATEWAY_ALLOW_ALL_USERS=true
hermes gateway stop
hermes gateway start
hermes gateway statusExpose only the intended endpoint
Use HTTPS, a private VPN, or an SSH tunnel that only trusted clients can reach. A Bearer token protects the request but does not make a publicly exposed agent runtime safe by itself.
Configure BenAgent
Set Provider to Hermes, replace the base URL with the private HTTPS or tunnel URL, and keep /v1/chat/completions unless you intentionally use the Responses endpoint.
OpenClaw remote checklist
Enable Chat Completions
OpenClaw must expose an OpenAI-compatible Chat Completions surface. Keep no-auth access on loopback, or align gateway.auth.token with the optional OpenClaw Bearer token in BenAgent Settings.
Keep tool locality explicit
If OpenClaw runs on a server, file tools and local commands run on that server. Do not expect a remote runtime to read your Mac desktop unless you intentionally sync or mount those files.
Send a BenAgent test message
Use a harmless prompt first. A successful reply proves the URL, endpoint path, private transport, model routing, and outbound network permission are aligned.
Remote runtime red flags
- The runtime works from curl on the server but not from the Mac. Check DNS, tunnel binding, and macOS outbound network access.
- The runtime can run shell tools against the wrong machine. Re-check where Hermes or OpenClaw is installed.
- The remote endpoint is reachable outside the trusted VPN or tunnel. Restrict the network boundary before using it from BenAgent.
- A public webhook URL is being reused as the chat endpoint. BenAgent chat requests and event delivery are separate paths.
References
Ready to bring agent-first work to your Mac?
Install BenAgent, connect Hermes or OpenClaw, verify the endpoint and its access boundary, then delegate one safe result you can review before relying on longer work.