Cairn

Telegram command parsing and argument handling fixes

NousResearch/hermes-agent · cluster 56323 · gateway

Data as of

4 open items. Fix attempted, not merged.

The short answer

2open issues
2open PRs
9items grouped
Known?
Yes. 9 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
2 issues and 2 PRs.

Multiple bugs and fixes related to Telegram slash commands losing arguments when a bot suffix (@botname) is present, plus related fixes for compact reasoning command parsing and platform base utility bugs.

Open issues2

  • Issue#56337[Bug]: Telegram strips /command@bot args into an unknown command
  • Issue#56910fix(telegram): slash command args lost in groups — @botname eats the space before arguments

Open PRs2

  • PR#33763fix: preserve Telegram command args after bot suffix
  • PR#56911fix(telegram): don't eat trailing space after @botname in _clean_bot_trigger_text

4 PRs closed without merging

From the close comments: duplicate 2 · other 2

  • #56324 fix(gateway): parse compact reasoning commands · other
  • #56338 fix(telegram): preserve args after command bot suffix · duplicate → #33763, #31126, #56337
  • #56471 fix(telegram): preserve slash-command args after @bot mention · duplicate → #33763
  • #105467 fix(telegram): keep the arguments of /command@bot in groups · other → #106742
Closed issues · 1
  • Closed#56323[Bug]: Telegram compact /reasoning level commands are rejected in groups
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.24: 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/56323.json
cluster/56323.md