hermes - 💡(How to fix) Fix [Feature]: Allow Feishu group chats to respond without requiring @mention [1 participants]

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…
GitHub stats
NousResearch/hermes-agent#12801Fetched 2026-04-20 12:16:54
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
closed ×1labeled ×1
RAW_BUFFERClick to expand / collapse

Background Currently, the Feishu gateway only processes group messages when the bot is explicitly @mention-ed. Any message without a mention is silently dropped. Need In certain deployment scenarios, requiring @mention is unnecessary or undesirable: Dedicated bot groups — where the group only contains the bot and no human-to-human conversation happens, so every message is implicitly directed at the bot Monitoring / logging use cases — where the bot should observe and respond to all group activity User preference — some teams simply prefer a conversational flow without needing to @mention every time It would be useful to have a configurable toggle that lets users choose whether @mention is required in group chats. Proposed Solution Add a require_mention boolean setting to the Feishu adapter: Default: true (current behavior — no breaking change) When set to false: all group messages pass the mention check and are routed to the agent normally Configuration Controlled via environment variable in ~/.hermes/.env: FEISHU_GROUP_REQUIRE_MENTION=false

Expected Behavior Note: Group access control (allowed users, admin rules) still applies independently of this setting. Implementation Sketch Add require_mention: bool = True to FeishuAdapterSettings Read from FEISHU_GROUP_REQUIRE_MENTION env var during adapter init In _require_group_message(), short-circuit to return True when require_mention is false Related Similar to Discord's existing require_mention / free_response_channels config pattern

extent analysis

TL;DR

To allow the Feishu gateway to process group messages without requiring an @mention, set the FEISHU_GROUP_REQUIRE_MENTION environment variable to false.

Guidance

  • Add a require_mention boolean setting to the Feishu adapter with a default value of true to maintain current behavior.
  • Control the require_mention setting via the FEISHU_GROUP_REQUIRE_MENTION environment variable in ~/.hermes/.env.
  • Update the _require_group_message() function to short-circuit and return true when require_mention is false, allowing all group messages to pass the mention check.
  • Ensure group access control (allowed users, admin rules) remains independent of this setting.

Example

class FeishuAdapterSettings:
    def __init__(self):
        self.require_mention = bool(os.getenv('FEISHU_GROUP_REQUIRE_MENTION', 'true') == 'true')

def _require_group_message(self):
    if not self.require_mention:
        return True
    # existing mention check logic

Notes

This solution assumes that the FEISHU_GROUP_REQUIRE_MENTION environment variable is properly set and read during adapter initialization. Additionally, this change may introduce security or access control implications, which should be carefully evaluated.

Recommendation

Apply the proposed workaround by setting FEISHU_GROUP_REQUIRE_MENTION to false, as it provides a configurable toggle for users to choose whether @mention is required in group chats.

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