A Runtime Readiness Checklist for Hermes and OpenClaw on macOS
Use this checklist to verify Hermes or OpenClaw before sending real work through BenAgent on macOS.
A local-first agent setup fails in predictable places: the runtime is not running, the endpoint path is wrong, the route still requires authentication, macOS permissions are missing, or the first prompt is too ambitious. Use this checklist before sending real work through BenAgent.
1. Confirm the runtime is running
- Hermes: verify the gateway status after editing ~/.hermes/.env.
- OpenClaw: verify the gateway status after enabling Chat Completions.
- Use the local port that matches the selected provider: 8642 for Hermes, 18789 for OpenClaw.
- Do not debug BenAgent first if the provider's own status command reports a stopped or unhealthy gateway.
2. Check endpoint values
Hermes default
Use the local Hermes base URL and Chat Completions path unless your gateway is hosted elsewhere.
Base URL: http://127.0.0.1:8642
Endpoint path: /v1/chat/completionsOpenClaw default
Use the local OpenClaw base URL and Chat Completions path after enabling the gateway endpoint.
Base URL: http://127.0.0.1:18789
Endpoint path: /v1/chat/completions3. Verify endpoint authentication
For trusted loopback access, both sides can use no auth. If the runtime expects a token, save the matching provider-scoped Bearer token in BenAgent Settings and test the exact configured URL.
4. Verify macOS permissions
- Network access must be available for the sandboxed app to reach the local endpoint.
- Microphone and speech recognition are only required for voice workflows, not for manual Quick Chat.
- If voice setup is blocked, test the agent from the manual message composer first so endpoint issues stay separate from permission issues.
5. Send a small first message
Start with a harmless prompt such as 'Reply with one sentence confirming the runtime is connected.' A small test proves the route, authentication, model, and visible reply path without mixing in tool execution or long-running automation.
Pass criteria
- BenAgent shows the selected provider as configured.
- The Test Agent action returns a visible answer.
- The runtime does not return 401, connection refused, empty reply, or silent placeholder text.
- The next message can use completed local history unless you intentionally reset the BenAgent conversation.
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.