Cairn
NousResearch/hermes-agent

Telegram polling conflicts and gateway behavior around hermes update

Cluster 23783 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

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

Most members concern Telegram bot token or polling conflicts that appear around hermes update, including one issue report and several proposed fixes involving retry/backoff, recovery, stale webhook deregistration, and an update-time warning when the gateway is running. The group appears largely related, though the webhook and background task result changes and the update warning are adjacent rather than identical themes.

Open issues0

No open issues.

Open PRs0

No open pull requests.

4 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1 · superseded by another PR 1 · won't fix / by design 1

  • #23793 fix(update): warn when gateway is running before hermes update · done elsewhere → f260aa6
  • #23806 fix(telegram): make polling conflict retryable with longer backoff · superseded by another PR → #25630, #23783
  • #25420 fix: deregister stale Telegram webhook, store bg task results · won't fix / by design → #23783, #23793, #23806, #8568, #8592
  • #25630 fix(telegram): recover from post-update polling conflict without entering limbo · merged via another change
Closed issues · 1
  • Closed#23783Telegram bot token already in use after hermes update — gateway fails to start, Telegram broken afterwards
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.40: 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
Closed issues
1
Attempts
4 PRs closed without merging

For your agent

The same facts, typed.

cluster/23783.json
cluster/23783.md