Capability matrix
What does each connection path cover?
The registry separates BenAgent transport and presentation from runtime capability.
| Connector | Endpoint | Authentication | Request and progress | Background results and images |
|---|---|---|---|---|
| Hermes Supported in BenAgent 1.3 Open setup guide | http://127.0.0.1:8642 /v1/chat/completions Local or intentionally remote user-controlled endpoint | Optional provider-scoped Bearer token stored in macOS Keychain and sent only to the selected Hermes endpoint. | One bounded BenAgent envelope containing completed local history and the current request. Progress: BenAgent can present supported streamed reply and tool/progress signals returned by the configured endpoint. | The repo-local Hermes delivery plugin can post supported cron or webhook results to BenAgent's loopback listener. Images: Current-turn image input and supported returned image output are retained through the BenAgent conversation path. |
| OpenClaw Supported in BenAgent 1.3 Open setup guide | http://127.0.0.1:18789 /v1/chat/completions Local or intentionally remote user-controlled endpoint | Optional provider-scoped Bearer token stored in macOS Keychain and sent only to the selected OpenClaw endpoint. | One bounded BenAgent envelope containing completed local history and the current request. Progress: BenAgent can present supported streamed reply and tool/progress signals returned by the configured endpoint. | The repo-local OpenClaw plugin can post supported owned cron or plugin results to BenAgent's loopback listener. Images: Current-turn image input and supported returned image output are retained through the BenAgent conversation path. |
Compatibility limits
What is explicitly not certified?
Hermes limitations
- Hermes owns models, tools, skills, files, memory, network access and execution.
- Provider-returned session identifiers do not own BenAgent conversation continuity.
- A remote Hermes endpoint changes the privacy and transport boundary.
- No specific Hermes runtime version is certified by this public record.
OpenClaw limitations
- OpenClaw owns models, tools, skills, files, memory, network access and execution.
- Provider-returned session identifiers do not own BenAgent conversation continuity.
- A remote OpenClaw endpoint changes the privacy and transport boundary.
- No specific OpenClaw runtime version is certified by this public record.
Unsupported connector claims
- No native Codex connection claimed.
- No native Claude Code connection claimed.
- No universal OpenAI-compatible-runtime guarantee.
Reproducible connection check
How should compatibility be verified?
- 01
Confirm the runtime endpoint
Start Hermes or OpenClaw and verify the configured HTTP endpoint is reachable from the Mac.
- 02
Align authentication
Keep trusted no-auth access on loopback or save the matching optional provider token in BenAgent Keychain settings.
- 03
Send a harmless bounded request
Check readiness, reply decoding, progress, and local conversation continuity before using private data or tools.
- 04
Test events separately
Interactive replies and background event delivery use different paths; verify the repo-local plugin only when background results are needed.
Frequently asked questions
Questions about BenAgent connections
Which agent runtimes does BenAgent support today?
BenAgent 1.3 has current connection paths for Hermes and OpenClaw. This registry does not claim native Codex, Claude Code, or arbitrary runtime support.
Does BenAgent install or host Hermes or OpenClaw?
No. The user runs and controls the runtime endpoint. BenAgent supplies connection setup, bounded request transport, readiness feedback, local continuity, progress, and result presentation.
Can a supported endpoint be remote?
Yes. Hermes or OpenClaw can be configured at an intentionally remote URL, but the user must secure transport, authentication, runtime permissions, and logs. A remote endpoint changes the privacy boundary.
Does BenAgent use runtime session IDs for continuity?
No. BenAgent continuity comes from completed local conversation records and a bounded history envelope. Provider-returned session identifiers can be decoded for compatibility but do not own the local conversation.
Does this registry certify every Hermes or OpenClaw version?
No. The record is verified against the current BenAgent version and does not publish a blanket runtime-version certification. Runtime changes still require a reproducible compatibility check.