Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix [Feature]: Expose a local WebSocket interface for third-party clients (e.g. CoClaw mobile app) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#11712•Fetched 2026-04-18 05:59:15
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
Antsoldier1974Antsoldier1974
Participants
Antsoldier1974Antsoldier1974
Timeline (top)
cross-referenced ×1

We are building a CoClaw plugin (@coclaw/hermes-coclaw) to let Hermes Agent users connect their agent to CoClaw — a native mobile app for AI agent collaboration, similar to how OpenClaw users connect via @coclaw/openclaw-coclaw.

To make this work, the plugin needs a stable local interface to interact with Hermes Agent at runtime. Currently, Hermes exposes:

  • ACP adapter (hermes acp) — designed for editor workflows, not a persistent message channel
  • Gateway platforms (Telegram, Discord, etc.) — designed for cloud messaging, not local plugin integration

Neither fits the use case of a local plugin acting as a real-time bridge between the user's mobile app and their Hermes Agent instance.

Root Cause

We are building a CoClaw plugin (@coclaw/hermes-coclaw) to let Hermes Agent users connect their agent to CoClaw — a native mobile app for AI agent collaboration, similar to how OpenClaw users connect via @coclaw/openclaw-coclaw.

To make this work, the plugin needs a stable local interface to interact with Hermes Agent at runtime. Currently, Hermes exposes:

  • ACP adapter (hermes acp) — designed for editor workflows, not a persistent message channel
  • Gateway platforms (Telegram, Discord, etc.) — designed for cloud messaging, not local plugin integration

Neither fits the use case of a local plugin acting as a real-time bridge between the user's mobile app and their Hermes Agent instance.

RAW_BUFFERClick to expand / collapse

Summary

We are building a CoClaw plugin (@coclaw/hermes-coclaw) to let Hermes Agent users connect their agent to CoClaw — a native mobile app for AI agent collaboration, similar to how OpenClaw users connect via @coclaw/openclaw-coclaw.

To make this work, the plugin needs a stable local interface to interact with Hermes Agent at runtime. Currently, Hermes exposes:

  • ACP adapter (hermes acp) — designed for editor workflows, not a persistent message channel
  • Gateway platforms (Telegram, Discord, etc.) — designed for cloud messaging, not local plugin integration

Neither fits the use case of a local plugin acting as a real-time bridge between the user's mobile app and their Hermes Agent instance.

Proposed Interface

A minimal local WebSocket server (similar to OpenClaw's Gateway WebSocket on ws://127.0.0.1:<port>), exposing:

MethodDescription
hermes.agents.listList active agents and their status
hermes.message.sendSend a message to an agent, stream the response
hermes.session.listList sessions for an agent
hermes.session.getGet message history for a session

Events pushed by the server:

EventDescription
agent.thinkingAgent is processing
agent.tool_callAgent is calling a tool
agent.doneAgent turn completed

Authentication via a local token (similar to OPENCLAW_GATEWAY_TOKEN).

Why Not ACP?

ACP is task-oriented and editor-driven — it works well for one-shot coding tasks but is not designed for persistent bidirectional messaging with streaming status updates across multiple agents.

Scope

This is a minimal ask — the interface only needs to cover:

  1. Agent enumeration
  2. Message send + streaming response
  3. Session history read (alternatively, the plugin can read ~/.hermes/state.db directly if a stable schema is documented)

File transfer does not require Hermes involvement — the CoClaw plugin handles it via WebRTC DataChannel directly on the local filesystem.

Related

— CoClaw Team 🤖 Don't have CoClaw yet? Visit coclaw.net to get started.

extent analysis

TL;DR

Implement a minimal local WebSocket server to provide a stable interface for the CoClaw plugin to interact with Hermes Agent.

Guidance

  • Investigate the feasibility of using the proposed WebSocket server interface to expose necessary methods (hermes.agents.list, hermes.message.send, hermes.session.list, hermes.session.get) and events (agent.thinking, agent.tool_call, agent.done) for real-time communication between the CoClaw plugin and Hermes Agent.
  • Consider implementing authentication via a local token, similar to OPENCLAW_GATEWAY_TOKEN, to secure the WebSocket server interface.
  • Evaluate the trade-offs of using the ACP adapter versus the proposed WebSocket server interface, considering the requirements for persistent bidirectional messaging and streaming status updates.
  • Review the scope of the proposed interface to ensure it meets the minimal requirements for agent enumeration, message sending, and session history reading.

Example

No code snippet is provided due to the lack of specific implementation details in the issue.

Notes

The proposed solution relies on the assumption that a minimal local WebSocket server can be implemented to provide the necessary interface for the CoClaw plugin. However, the issue does not provide information on the technical feasibility or potential challenges of implementing such a server.

Recommendation

Apply workaround: Implement a minimal local WebSocket server to provide the necessary interface for the CoClaw plugin, as the proposed solution seems to be the most feasible approach given the requirements and constraints described in the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#chain error#conversation history#tool integration#LLM response#prompt template

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING