Cairn
NousResearch/hermes-agent

Telegram bot token format validation at gateway setup

Cluster 9843. Data as of

Nothing open on GitHub. Fix merged in #10613 on 16 Apr 2026. Check it covers your case.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #10613. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and pull requests concern adding or fixing validation of the Telegram bot token format during the gateway setup process. Two fix PRs and one bug report address the same specific validation gap.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #10613 fix: validate Telegram bot token format during gateway setup (#9964)

    merged to main

    files: hermes_cli/setup.py

    Show the diff
    • hermes_cli/setup.py
      @@ -1611,9 +1611,19 @@ def _setup_telegram():
             return
 
     print_info("Create a bot via @BotFather on Telegram")
-    token = [redacted:secret-assignment]"Telegram bot token", password=True)
-    if not token:
-        return
+    import re
+
+    while True:
+        token = [redacted:secret-assignment]"Telegram bot token", password=True)
+        if not token:
+            return
+        if not re.match(r"^\d+:[A-Za-z0-9_-]{30,}$", token):
+            print_error(
+                "Invalid token format. Expected: <numeric_id>:<alphanumeric_hash> "
+                "(e.g., 123456789:ABCdefGHI-jklMNOpqrSTUvwxYZ)"
+            )
+            continue
+        break
     save_env_value("TELEGRAM_BOT_TOKEN", token)
     print_success("Telegram token saved")

1 PR closed without merging

From the close comments: merged via another change 1

  • #9964 fix: validate Telegram bot token format during gateway setup (#9843) · merged via another change → #10613
Closed issues · 1
  • Closed#9843bug: gateway setup does not validate Telegram bot token format
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

Merged PRs
#10613
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
16 Apr 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.

For your agent

The same facts, typed.

cluster/9843.json
cluster/9843.md