NousResearch/hermes-agent

Gateway platform-lock conflicts and stale-state recovery

Cluster 65176 · gateway. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #68652 on 21 Jul 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #68652. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #68652. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #68652, then check it covers your case.

Read #68652 Pick up a Lab task

These items concern gateway processes entering restart loops or failure states due to Telegram token conflicts, stale platform locks, and lingering state after restarts. Work spans detection, backoff behavior, lock takeover on replace, and clearing stale buffers across Telegram and Weixin adapters.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#68652 fix(gateway): --replace takes over live platform-lock holders once and reaps orphaned children

merged to main

files: contributors/emails/[redacted:email], gateway/platforms/base.py, gateway/run.py, gateway/status.py, tests/gateway/test_replace_child_reap.py, tests/gateway/test_runner_startup_failures.py, tests/gateway/test_stale_platform_lock_retryable.py, tests/gateway/test_status.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

#65178 fix(gateway): take over live platform-lock token holders once · merged via another change → #68652
#65191 fix(gateway): take over scoped token lock on replace · done elsewhere → #65176, #68652, #65178

Closed issues · 1

Closed#65176Gateway doesn't auto-resolve Telegram token conflict at platform connect — waits for manual SIGKILL

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: gateway
Merged PRs: #68652
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 21 Jul 2026

For your agent

The same facts, typed.

cluster/65176.json
cluster/65176.md