mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-11-16 19:36:54 +00:00
Settings -> Passwords & Logins dialed every vault RPC through requestGatewayForProfile(scopeProfile): a bare profile name. gatewayForProfile resolves a bare name equal to the primary profile onto the PRIMARY socket, so with two connections both serving `default` the panel shown for "This device" was answered by the other machine -- "Not detected" for a manager that is installed locally, and vault.unlock/vault.add landing in the remote vault (#94811, piskooooo's follow-up). The panel already keys itself by (connectionId, profile); its RPCs now go through requestGatewayForAgent with that same connectionId, which keeps a same-named non-primary connection on its own pooled socket. A null connectionId (single-connection v1 route) still takes the profile door, so single-source installs are unchanged. Co-authored-by: Lorencato <[email protected]>
1 line
12 B
Text
1 line
12 B
Text
lorencato23
|