hermes - ✅(Solved) Fix Telegram /sethome loses forum topic thread ID and cron deliver=telegram prefers origin over home [1 pull requests, 1 participants]

hermes2026-05-02 18:53:48

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.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

NousResearch/hermes-agent#18934•Fetched 2026-05-03 04:53:30

View on GitHub

Comments

Participants

Timeline

Reactions

Author

barronlroth

Participants

barronlroth

Timeline (top)

labeled ×5cross-referenced ×1

Code Example

telegram:<chat_id>:<thread_id>

---

deliver: telegram

---

TELEGRAM_HOME_CHANNEL=<chat_id>

---

if platform_name == deliver_value:
    if origin and origin.get("platform") == platform_name:
        return {
            "platform": platform_name,
            "chat_id": str(origin["chat_id"]),
            "thread_id": origin.get("thread_id"),
        }

---

deliver: telegram
origin: telegram DM topic 13868
TELEGRAM_HOME_CHANNEL: group chat -1003984902686

---

telegram:-1003984902686:1

RAW_BUFFERClick to expand / collapse

Bug Description

Telegram home-channel delivery does not reliably work for forum topics, and cron delivery semantics for bare deliver: "telegram" are surprising/misleading.

There appear to be two related problems:

/sethome stores only the Telegram chat_id, not the message_thread_id, so setting home from inside a Telegram forum topic loses the topic/thread.
Cron jobs with deliver: "telegram" route to the job's same-platform origin before falling back to TELEGRAM_HOME_CHANNEL, which contradicts the user-facing/docs impression that a bare platform name means the configured platform home channel.

This is related to, but distinct from, #8866. That issue covers explicit delivery being influenced by home-channel state. This issue is about (a) home not preserving Telegram topic/thread information and (b) bare telegram preferring origin over home.

Expected Behavior

If /sethome is run in a Telegram forum topic, Hermes should persist enough information to deliver future cron/cross-platform messages back to that exact topic.

For example, home should effectively support:

telegram:<chat_id>:<thread_id>

Cron jobs with:

deliver: telegram

should deliver to the configured Telegram home destination, including thread/topic if configured. If origin-first behavior is intentional, docs and /sethome copy should say so clearly.

Actual Behavior

/sethome saves only the chat id:

TELEGRAM_HOME_CHANNEL=<chat_id>

It does not persist message_thread_id.

Additionally, cron delivery resolution for bare telegram prioritizes same-platform job origin before platform home:

if platform_name == deliver_value:
    if origin and origin.get("platform") == platform_name:
        return {
            "platform": platform_name,
            "chat_id": str(origin["chat_id"]),
            "thread_id": origin.get("thread_id"),
        }

In a real case, a cron job had:

deliver: telegram
origin: telegram DM topic 13868
TELEGRAM_HOME_CHANNEL: group chat -1003984902686

Target resolution returned the origin DM topic instead of the configured Telegram home channel.

The workaround was to make the cron target explicit:

telegram:-1003984902686:1

Reproduction

Use Hermes gateway in a Telegram group/forum topic.
Run /sethome from topic 1.
Observe that TELEGRAM_HOME_CHANNEL stores only the group chat ID, not the topic/thread ID.
Create a cron job from another Telegram chat/topic with deliver: "telegram".
Observe that delivery resolves to the job's Telegram origin rather than the configured home channel.

Suggested Fix

Extend the home-channel model to preserve optional thread_id / Telegram message_thread_id.
Update /sethome to save topic/thread information when available.
Update cron delivery semantics so bare platform delivery (telegram) truly means platform home, or update docs/command copy if origin-first behavior is intentional.
Add tests covering:
- /sethome in a Telegram forum topic persists thread id.
- deliver: "telegram" resolves to Telegram home, not same-platform origin, when home is configured.
- Explicit deliver: "telegram:<chat_id>:<thread_id>" continues to bypass home/origin and targets the exact topic.

Environment

Hermes Agent: current main checkout
Platform: Telegram gateway
Scenario: cron jobs delivering to Telegram forum topics

Impact

Medium/high for users relying on Telegram forum topics for scheduled reports. The current behavior makes /sethome look successful while cron reports silently land in the wrong Telegram topic/chat, or lose the topic entirely.

extent analysis

TL;DR

Update the home-channel model to preserve the optional thread_id and modify the /sethome command to save topic/thread information when available to fix the Telegram home-channel delivery issue.

Guidance

Extend the home-channel model to store both chat_id and thread_id for Telegram to ensure accurate delivery to forum topics.
Modify the /sethome command to save the message_thread_id when setting the home channel from within a Telegram forum topic.
Update the cron delivery semantics to prioritize the configured Telegram home channel over the job's origin when deliver is set to "telegram".
Add tests to cover the persistence of thread IDs by /sethome, the resolution of deliver: "telegram" to the Telegram home channel, and the behavior of explicit delivery specifications.

Example

No code snippet is provided as the issue description does not imply a specific code change but rather a design and functionality update.

Notes

The suggested fix involves updating the home-channel model and the /sethome command, which may require additional testing to ensure backward compatibility and correct functionality across different scenarios.

Recommendation

Apply the workaround by explicitly specifying the delivery target in the cron job configuration, such as deliver: "telegram:<chat_id>:<thread_id>", until the underlying issue is addressed by updating the home-channel model and delivery semantics.

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?

#environment setup #docker error #permission error #memory optimization #batch processing

Still need to ship something?

×6

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

hermes - ✅(Solved) Fix Telegram /sethome loses forum topic thread ID and cron deliver=telegram prefers origin over home [1 pull requests, 1 participants]

Recommended Tools

GitHub issue graph ai analysis

Fix Action

Fix / Workaround

PR fix notes

PR #19014: fix(gateway,cron): persist Telegram forum topic on /sethome

Description (problem / solution / changelog)

What does this PR do?

Related Issue

Type of Change

Changes Made

How to Test

Checklist

Code

Documentation & Housekeeping

Changed files