hermes - 💡(How to fix) Fix Feature request: Configurable Telegram bot command menu order

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Fix Action

Fix / Workaround

Use Case

My most-used workflow commands (/background, /steer, /queue) are buried mid-menu. I want them at the top. The only option today is patching the source, which gets overwritten on every hermes update.

Current Workaround

I wrote a script that calls the Telegram Bot API setMyCommands directly after gateway startup to override the order. It works but is fragile:

  • Fetches commands via getMyCommands
  • Reorders them client-side
  • Pushes back via setMyCommands
  • Needs a cron job to reapply after updates/restarts

Alternatives Considered

  • Source patch: fragile, root-required, wiped on update
  • Bot API hack (current): works but adds latency and maintenance overhead
  • Plugin hook: overkill for a config value
RAW_BUFFERClick to expand / collapse

Problem

The Telegram bot command menu order is hardcoded in hermes_cli/commands.py via _TELEGRAM_MENU_PRIORITY. Users cannot customize which commands appear first in the slash-command hint menu without editing source code.

Use Case

My most-used workflow commands (/background, /steer, /queue) are buried mid-menu. I want them at the top. The only option today is patching the source, which gets overwritten on every hermes update.

Current Workaround

I wrote a script that calls the Telegram Bot API setMyCommands directly after gateway startup to override the order. It works but is fragile:

  • Fetches commands via getMyCommands
  • Reorders them client-side
  • Pushes back via setMyCommands
  • Needs a cron job to reapply after updates/restarts

Proposed Solution

A config option in config.yaml:

telegram: menu_priority: - background - steer - queue - help - new

Commands in the list get ordered first; unlisted commands fall back to alphabetical after the explicit entries. This mirrors how _TELEGRAM_MENU_PRIORITY already works internally.

Alternatives Considered

  • Source patch: fragile, root-required, wiped on update
  • Bot API hack (current): works but adds latency and maintenance overhead
  • Plugin hook: overkill for a config value

The config approach is minimal, backward-compatible (empty list = stock behavior), and consistent with how other Hermes features are configured.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix Feature request: Configurable Telegram bot command menu order