When configuring specific WhatsApp groups to not require mentions (requireMention: false), unmentioned messages in those groups are not forwarded to Claude, despite the config being correct.
Config:
{
"whatsapp": {
"allowFrom": ["+1234567890"],
"groups": {
"*": { "requireMention": true },
"<GROUP_JID>@g.us": { "requireMention": false }
}
},
"routing": {
"groupChat": {
"mentionPatterns": ["@botname", "botname"]
}
}
}Observed behavior:
- Messages WITH mention patterns → forwarded correctly ✅
- Messages WITHOUT mention patterns → NOT forwarded ❌
Debug info from logs:
"group mention debug": {
"conversationId": "<GROUP_JID>@g.us",
"wasMentioned": false,
"body": "test message without mention"
}
The message arrives, wasMentioned: false is logged, conversationId matches the config exactly, but no forwarding occurs.
Troubleshooting done:
- Verified JSON parses correctly (no fancy quotes/unicode)
- Verified JID in config matches
conversationId in logs exactly
- Cleared
sessions.json and restarted gateway
- Multiple gateway restarts after config changes
Clawdis version: 2.0.0-beta5
Suspected cause:
Per Discord discussion with @Clawd, the resolveGroupRequireMentionFor() function in auto-reply.ts may not be correctly looking up the group config, or session store values may be overriding config values.
This issue was drafted by BenBot 🤖 (my Clawdis AI agent) and reviewed by me before posting.
When configuring specific WhatsApp groups to not require mentions (
requireMention: false), unmentioned messages in those groups are not forwarded to Claude, despite the config being correct.Config:
{ "whatsapp": { "allowFrom": ["+1234567890"], "groups": { "*": { "requireMention": true }, "<GROUP_JID>@g.us": { "requireMention": false } } }, "routing": { "groupChat": { "mentionPatterns": ["@botname", "botname"] } } }Observed behavior:
Debug info from logs:
The message arrives,
wasMentioned: falseis logged, conversationId matches the config exactly, but no forwarding occurs.Troubleshooting done:
conversationIdin logs exactlysessions.jsonand restarted gatewayClawdis version: 2.0.0-beta5
Suspected cause:
Per Discord discussion with @Clawd, the
resolveGroupRequireMentionFor()function inauto-reply.tsmay not be correctly looking up the group config, or session store values may be overriding config values.This issue was drafted by BenBot 🤖 (my Clawdis AI agent) and reviewed by me before posting.