hermes - 💡(How to fix) Fix [Feature]: Single central agent/server with multiple clients [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#14197Fetched 2026-04-23 07:46:09
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Participants
Timeline (top)
labeled ×4
RAW_BUFFERClick to expand / collapse

Problem or Use Case

I have hermes running on a Pi4. It is able to save my preferences and follow accordingly while working on tasks, like modifying files on disk. However, when I am working on a different device, as I could not use the same agent, I have to set up a brand new agent and start from scratch or copy over the .hermes dir and set up sync, which can be a bad idea depending on latency.

Proposed Solution

If the hermes cli can support connecting to existing agent running on a device on the network, it would be extremely helpful to integrate multiple devices with single agent. A central memory store, skills, tools etc. eg: hermes connect http://10.0.010:1234

Alternatives Considered

No response

Feature Type

CLI improvement

Scope

None

Contribution

  • I'd like to implement this myself and submit a PR

Debug Report (optional)

extent analysis

TL;DR

To integrate multiple devices with a single Hermes agent, consider implementing a feature to connect to an existing agent running on a device on the network.

Guidance

  • Investigate the feasibility of adding a connect command to the Hermes CLI to link to an existing agent on the network.
  • Research potential solutions for a central memory store to manage skills, tools, and other data across devices.
  • Consider the security implications of connecting to an existing agent, such as authentication and authorization.
  • Evaluate the potential impact on latency and performance when connecting to a remote agent.

Example

No code example is provided as the issue lacks specific technical details.

Notes

The proposed solution requires further investigation into the technical feasibility and potential security concerns. The issue lacks information on the current architecture and technical limitations of the Hermes agent.

Recommendation

Apply workaround: Implement a feature to connect to an existing agent running on a device on the network, as it would allow for better integration of multiple devices with a single agent, but ensure to address potential security and performance concerns.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix [Feature]: Single central agent/server with multiple clients [1 participants]