Cairn
NousResearch/hermes-agent

Telegram forum topic renaming fixes and features

Cluster 57341 · gateway. 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.

These members address automatic renaming of Telegram forum topics when session titles change, covering edge cases like runtime-discovered DMs, manual /title commands, and sessions where the first message is a voice or audio message.

Open issues1

  • Issue#57341Telegram topic remains unnamed ('New Thread') when first message is a voice/audio message

Open PRs1

  • PR#58430fix(telegram): rename runtime-discovered DM topics

2 PRs closed without merging

From the close comments: merged via another change 1 · other 1

  • #9921 feat(telegram): auto-rename forum topics on session title change · other → 38f1a92
  • #49172 fix(gateway): rename the Telegram topic from /title, not only auto-titles · merged via another change → 38f1a92, #49245, #35678, #46644, #21111, #14462
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
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/57341.json
cluster/57341.md