Cairn
NousResearch/hermes-agent

Per-topic Telegram toolset scoping bug and fix

Cluster 37743 · gateway. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

A bug where per-topic enabled_toolsets configuration in Telegram group topics was parsed but not enforced, causing all topics to load the same full toolset. The members cover the bug report and corresponding fix to properly scope toolsets per topic.

Open issues1

  • Issue#37743[Bug] per-topic `enabled_toolsets` in `telegram.group_topics` is parsed but never enforced — all topics load identical full toolset

Open PRs2

  • PR#37767fix(gateway): scope Telegram topic toolsets per topic
  • PR#37922fix(gateway): enforce per-topic enabled_toolsets for Telegram group_topics
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.67: 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
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/37743.json
cluster/37743.md