hermes - 💡(How to fix) Fix [Feature] Per-conversation background sessions for long-running tasks (Feishu DM / Telegram Topics) [1 participants]

Problem

When Hermes Agent receives a message on Feishu DM or Telegram DM and starts a long-running task, the user cannot send follow-up messages without interrupting the task. There is no way to background the task within the same conversation in a non-blocking way.

Platform limitations:

• Feishu: One user = one bot conversation queue. Messages are processed sequentially. No multi-session support.
• Telegram: Supports Forum/Topics (multi-threaded), but Hermes does not create isolated sessions per topic.

Desired behavior

• For Telegram: Detect is_topic_message and create one session per topic, similar to how Discord threads work.
• For Feishu: Implement reliable /bg command that spawns a background sub-session without interrupting the running task.
• Auto-detection of long-running tasks (e.g. >30s) and automatic background spawning.

Use case

User on Feishu starts a report generation task that takes 30+ seconds. User wants to ask a follow-up question while the report is still generating, without blocking or losing context.

Technical notes

This appears to require changes at the platform adapter layer (Feishu/Telegram adapters) to expose session/thread metadata to the agent, so the skill layer can implement the sub-session logic. Currently skills cannot access platform-specific conversation context (topic ID, thread ID, etc.).

• Hermes Agent version: latest
• Platform: Feishu DM, Telegram DM
• Related: ACP list_sessions does not expose per-platform session metadata