@Teknium@chrisbward so SSH seems like a partial answer. I think the remaining distinction is conceptual: remote execution is one thing, but a node model is closer to “this same agent can operate through this device’s own capabilities” rather than just opening a shell there. @NousResearch
@Teknium@chrisbward my concern was never just “how do I run commands on another machine?”. It was more: how do I avoid ending up with multiple Hermes installs that feel like multiple separate agents, each with their own memory/config/state? 👇
@Teknium@chrisbward what I like in the gateway + nodes OpenClaw's approach is the idea of one agent identity that expands across devices. The important part is not only execution, but ATTACHED capabilities: local tools, local context, device-native integrations, etc.
@Teknium@chrisbward Thanks, really appreciate the reply :)
SSH backend definitely helps, because it means I could keep one Hermes running 24/7 on the VPS and still have it execute things on my Mac. but... 👇
@Teknium@chrisbward Hermes feels so stable and clean imo, I'm enjoying it a lot! But it's like trapped in the VPS, and if I install it too on another device, I feel that there are 2 complete different entities
https://t.co/TbL7pRCJEZ
@Teknium@chrisbward This works pretty well in OC, where we can have a single gateway and pair nodes (devices) to to it. All the messages reaches the gateway, but he can perform things and can have access in the nodes. So one single instance, memory, config, etc... growing and expanding