BenAgent connection option · OpenClaw
Use OpenClaw from a focused Mac workspace.
Use BenAgent to delegate a focused request to the OpenClaw runtime you control, follow live progress, keep bounded conversation context on your Mac, and receive cron or plugin 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
OpenClaw is one connection option inside BenAgent.
Choosing OpenClaw does not redefine BenAgent around one runtime. OpenClaw still owns models, tools, skills, files, and gateway execution while BenAgent provides the focused macOS surface for requests, readiness, local conversation continuity, and local event delivery.
Connects to your configured OpenClaw base URL and endpoint path.
Sends bounded local history inside one user message and does not rely on a provider-owned session identifier.
Shows provider and network readiness before a real request starts.
Can receive finished cron and plugin events through BenAgent's local event listener.
Setup path
Connect OpenClaw without hiding who owns the work.
Start with a reachable OpenClaw gateway
Confirm the gateway answers locally or from the Mac before adding BenAgent. The common local base URL is http://127.0.0.1:18789, with the endpoint path configured separately.
Align the endpoint access boundary
Keep trusted no-auth access on loopback, or configure gateway.auth.token and save the same optional OpenClaw Bearer token in BenAgent. Do not expose an unauthenticated endpoint publicly.
Verify readiness and send a safe test
Use the Setup and Diagnostics surfaces to check endpoint construction, sandbox network access, and provider readiness before sending real work data.
Add event delivery only when needed
Install the BenAgent OpenClaw plugin when cron or plugin completion events should appear on the Mac. Prompt traffic and event delivery remain separate paths.
Choose by job
Use OpenClaw's app to manage the runtime; add BenAgent to keep delegated work beside other Mac apps.
Use the official OpenClaw macOS experience when you want the first-party companion for that runtime. Add BenAgent when you want one lightweight surface that can sit across OpenClaw and Hermes, preserve local conversation context, and show BenAgent-specific readiness or event delivery.
Choose the official OpenClaw app
Best when your desktop workflow is centered on OpenClaw and you want its first-party runtime controls and platform integration.
Add BenAgent
Best when you already control an endpoint and want outcome-first requests, live progress, cross-runtime selection, and local cron/plugin results beside other work.
Trust boundary
OpenClaw remains in charge.
- BenAgent does not host OpenClaw, choose its model, or grant tools access. Those decisions stay with the runtime.
- Prompts go from the Mac to the endpoint you configure; there is no BenAgent prompt relay server in the middle.
- The OpenClaw event plugin is a separate optional integration and its source is available publicly for review.
Put it into practice