Summary
In Feishu topic/thread conversations, Hermes currently splits a single interaction across multiple topics: the final answer usually returns to the original topic, but intermediate progress messages (tool progress, status updates, processing messages) can create new topics instead of staying in the original one.
Expected behavior
When a user mentions Hermes inside an existing Feishu topic, the entire lifecycle of that request should remain inside that same topic, including:
- tool progress
- status updates
- processing/intermediate messages
- final answer
Hermes should not create additional topics during processing.
Actual behavior
Observed behavior:
- User mentions Hermes in an existing Feishu topic
- Hermes starts processing
- Intermediate/progress messages appear in newly created topics
- Final answer appears back in the original topic
This causes one logical conversation to be split across multiple Feishu topics.
Reproduction conditions
- Platform: Feishu
- Context: topic / thread / forum-style group conversation
- Trigger: mention Hermes inside an existing topic
- More visible when tool progress / status output is enabled
Analysis
This looks like a Feishu topic/thread routing inconsistency between different outbound message paths:
- The final reply path appears to correctly bind the response back to the original topic.
- The intermediate progress/status path does not appear to use an equally strong topic-binding strategy, so Feishu treats those messages as new topic/thread entries.
In other words, Hermes seems to partially support Feishu topics for final replies, but not for the full execution lifecycle.
Why this matters
For topic-based workflows, users expect the entire conversation to stay scoped to one topic. Creating extra topics during execution makes the conversation fragmented and hard to follow.
Suggested fix direction
Please ensure that all outbound messages associated with a request originating from a Feishu topic use a consistent topic/thread routing strategy, not just the final answer. This should apply to:
- tool progress messages
- status updates
- intermediate processing messages
- final response
Acceptance criteria
- Mention Hermes inside an existing Feishu topic
- Hermes processes the request without creating any new topics
- All intermediate and final messages stay inside the original topic
- Multi-turn follow-ups in the same topic remain stable and do not fork into new topics
Temporary workaround
Disabling Feishu tool progress/output reduces the symptom, but does not solve the underlying issue.
Summary
In Feishu topic/thread conversations, Hermes currently splits a single interaction across multiple topics: the final answer usually returns to the original topic, but intermediate progress messages (tool progress, status updates, processing messages) can create new topics instead of staying in the original one.
Expected behavior
When a user mentions Hermes inside an existing Feishu topic, the entire lifecycle of that request should remain inside that same topic, including:
Hermes should not create additional topics during processing.
Actual behavior
Observed behavior:
This causes one logical conversation to be split across multiple Feishu topics.
Reproduction conditions
Analysis
This looks like a Feishu topic/thread routing inconsistency between different outbound message paths:
In other words, Hermes seems to partially support Feishu topics for final replies, but not for the full execution lifecycle.
Why this matters
For topic-based workflows, users expect the entire conversation to stay scoped to one topic. Creating extra topics during execution makes the conversation fragmented and hard to follow.
Suggested fix direction
Please ensure that all outbound messages associated with a request originating from a Feishu topic use a consistent topic/thread routing strategy, not just the final answer. This should apply to:
Acceptance criteria
Temporary workaround
Disabling Feishu tool progress/output reduces the symptom, but does not solve the underlying issue.