Cairn
NousResearch/hermes-agent

Telegram command menu cap and priority ordering

Cluster 33480 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
7items grouped
Known?
Yes. 7 related items grouped here, 2 issues already closed.
Fix event
No fix has been merged to main. 5 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.

These issues and PRs address two related problems: the Telegram bot command menu's low cap (30 commands) cutting off plugin slash commands, and the ordering logic that determines which commands appear when the cap is reached. Multiple approaches to raising the limit and enforcing priority are represented.

Open issues0

No open issues.

Open PRs0

No open pull requests.

5 PRs closed without merging

From the close comments: done elsewhere 3 · closed without comment 1 · duplicate 1

  • #33484 fix(telegram): raise command menu cap from 30 to 100 so plugin commands appear · done elsewhere → dbe14ce, d4be583
  • #33706 fix(cli): prioritize plugin commands above skills in Telegram menu · done elsewhere → d4be583, dbe14ce, #42021
  • #40325 fix(cli): prioritize Telegram plugin commands · done elsewhere → dbe14ce, d4be583, #40305
  • #42021 feat(gateway): configure Telegram command menu priority · closed without comment
  • #49017 fix(telegram): bump MAX_COMMANDS_PER_SCOPE from 30 to 75 · duplicate → #33484
Closed issues · 2
  • Closed#33480Bug: Plugin slash commands truncated by 30-command cap in Telegram menu
  • Closed#40305Plugin slash commands can never appear in the Telegram command menu despite "take precedence / never trimmed"
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.26: 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
2
Attempts
5 PRs closed without merging

For your agent

The same facts, typed.

cluster/33480.json
cluster/33480.md