BenAgent connection option · Hermes
Use Hermes Agent from a native Mac workspace.
Use BenAgent as the native Mac layer for delegating a focused request to the Hermes API server you control, following live progress, and receiving replies or automation results beside your work.
Free download for macOS 14+. Normal voice and agent use requires a one-time US $9.99 Full Unlock; storefront pricing may vary.
Download BenAgentWhy it fits
Hermes is one connection option inside BenAgent.
Choosing Hermes does not redefine BenAgent around one runtime. Hermes keeps its model providers, tools, skills, files, and execution while BenAgent owns the focused Mac interaction, bounded local conversation, readiness feedback, and result visibility.
Connects to a local or intentionally remote Hermes API server.
Sends an optional provider-scoped Bearer token only when you configure one in BenAgent.
Sends bounded local history inside one user message instead of relying on a returned Hermes session identifier.
Can show Hermes cron or webhook results delivered to the local event listener.
Setup path
Prove the Hermes path before delegating real work.
Start the Hermes API server
Confirm Hermes is running and exposes its OpenAI-compatible server. The common local base URL is http://127.0.0.1:8642, with the endpoint path configured in BenAgent.
Align the endpoint access boundary
Keep trusted local no-auth access on loopback, or configure API_SERVER_KEY and save the same optional Hermes Bearer token in BenAgent. Do not expose an unauthenticated endpoint to the public internet.
Check endpoint and network readiness
Review the endpoint preview and diagnostics, then send a harmless test message before real prompts or files enter the workflow.
Route automation results deliberately
When a Hermes cron job or webhook should appear on the desktop, target BenAgent's local event listener rather than assuming chat replies and background events share one channel.
Choose by job
Use Hermes Desktop to manage Hermes; add BenAgent to keep delegated work beside other Mac apps.
The Hermes desktop experience is the direct choice for managing Hermes itself. BenAgent is useful when the runtime is already configured and you want a quiet floating surface that can also switch to OpenClaw and receive BenAgent event deliveries.
Choose Hermes Desktop
Best when you want the official Hermes experience for installation, configuration, runtime control, and Hermes-specific workflows.
Add BenAgent
Best when Hermes already answers through its API server and you want outcome-first requests, live progress, cross-runtime selection, and local result visibility beside other apps.
Trust boundary
Hermes still owns capability and data access.
- BenAgent does not select the Hermes model provider or decide which tools and skills Hermes may use.
- A remote Hermes URL changes the security boundary. Require a trusted private transport, configure the optional gateway token when needed, and verify TLS, access controls, and logs.
- Voice capture and desktop event delivery are BenAgent surfaces; actual task execution remains inside Hermes.
Put it into practice