OpenClaw (lobster) does not respond in the group, and checks three things first: whether the group is allowed, whether the person who sent the message is allowed, and whether mentions are needed. Common logs mention required, blocked, and allowlist in official troubleshooting basically point to group permission configuration.
Group chats must go through two doors at the same time
- Group itself:
channels.telegram.groupsor the group's configuration for the corresponding channel to allow this group. - Speaker:
groupAllowFromorallowFromto allow this user. - Trigger method: If
requireMentionis configured, the message must be bot or conform to mentionPatterns.
Telegram is a particularly easy pit to step on
Telegram group IDs are usually negative and should be placed in groups; The user ID is positive and should be placed in allowFrom or groupAllowFrom. If you write the group ID into groupAllowFrom, OpenClaw will treat it as "the speaker is not legitimate", so the group seems to be unresponsive.
It is recommended to configure the policy
Personal use suggestions "group allowlist + requireMention" to wake up lobsters in the group without triggering the agent with every sentence. It is best to create a separate business account and an independent gateway, rather than directly throwing personal assistants into a large group.
Official open source address: https://github.com/openclaw/openclaw.
When troubleshooting, it is best to verify in a small test group first, and do not change the configuration repeatedly in a large group. Only change one variable at a time: first confirm the group ID, then the user ID, and finally confirm the mention rule, so that it is easiest to locate which door has not passed.