Cairn
NousResearch/hermes-agent

Sibling profile gateway restarts during update and environment/credential handling

Cluster 135792 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

Members center on hermes update restarting sibling profile gateways, including a report that the updater's environment (e.g., a root TELEGRAM_BOT_TOKEN) can reach API-only profiles, and several PRs about respawning gateways with their own credentials. One member appears adjacent, concerning drain acknowledgment and already_stopping behavior rather than credentials.

Open issues1

  • Issue#135792hermes update restarts sibling profile gateways with the updater env: root TELEGRAM_BOT_TOKEN leaks into API-only profiles

Open PRs1

  • PR#135885fix(gateway): respawn sibling profile gateways without the updater's env

2 PRs closed without merging

From the close comments: closed without comment 1 · duplicate 1

  • #135877 fix(update): scope a restarted sibling profile to its own credentials (#135792) · duplicate → c578c3e, dc12dd1, c604742, #135877
  • #135913 fix(update): only the gateway's pausing is a drain ACK; already_stopping stops now · closed without comment
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
hermes cli
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/135792.json
cluster/135792.md