Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: groupPolicy: "open" ignored — WhatsApp group messages silently dropped at applyGroupGating despite correct config [1 pull requests, 3 comments, 2 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
openclaw/openclaw#49343•Fetched 2026-04-08 00:56:15
View on GitHub
Comments
3
Participants
2
Timeline
7
Reactions
0
Author
jgilb17jgilb17
Participants
jgilb17jgilb17RyceRyce
Timeline (top)
commented ×3labeled ×2cross-referenced ×1referenced ×1

Environment:

OpenClaw 2026.3.8 and 2026.3.13 (both tested), macOS, npm install Node v24.14.0 WhatsApp channel: linked, running, connected (personal number with selfChatMode: true)

JSON · 10 lines jsonCopyCopied! "whatsapp": { "enabled": true, "dmPolicy": "allowlist", "selfChatMode": true, "allowFrom": ["+17604139426"], "groupPolicy": "open", "ackReaction": { "direct": true, "group": "always" }, "debounceMs": 0, "mediaMaxMb": 50 }

Error Message

Observed: Message appears in logs as web-inbound, then hits applyGroupGating and is silently dropped. No agent turn triggered. No error. Every inbound group message is received (web-inbound logged), passes to applyGroupGating, and is silently dropped. The log ends there — no agent turn is triggered, no error, no further output. wasMentioned: false throughout.

Root Cause

Environment:

OpenClaw 2026.3.8 and 2026.3.13 (both tested), macOS, npm install Node v24.14.0 WhatsApp channel: linked, running, connected (personal number with selfChatMode: true)

JSON · 10 lines jsonCopyCopied! "whatsapp": { "enabled": true, "dmPolicy": "allowlist", "selfChatMode": true, "allowFrom": ["+17604139426"], "groupPolicy": "open", "ackReaction": { "direct": true, "group": "always" }, "debounceMs": 0, "mediaMaxMb": 50 }

Fix Action

Fixed

PR fix notes

PR #49651: fix: groupPolicy "open" no longer silently drops group messages

Description (problem / solution / changelog)

Summary

  • When groupPolicy: "open" is configured without explicit requireMention settings, resolveChannelGroupRequireMention now defaults to false instead of true, so group messages are not silently dropped by mention gating.
  • Previously, all group messages were received but then dropped at the mention gate because requireMention always defaulted to true regardless of the group policy mode.
  • Adds regression tests for the resolveChannelGroupRequireMention function covering the "open", "allowlist", and explicit requireMention override cases.

Closes #49343

Test plan

  • Existing group-policy.test.ts tests continue to pass (16 tests)
  • Existing web-auto-reply-monitor.test.ts tests continue to pass (13 tests)
  • New tests verify: groupPolicy: "open" defaults requireMention to false; groupPolicy: "allowlist" still defaults to true; explicit requireMention: true in groups config is respected even with groupPolicy: "open"

🤖 Generated with Claude Code

Changed files

  • src/config/group-policy.test.ts (modified, +64/-1)
  • src/config/group-policy.ts (modified, +8/-0)
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Summary

Environment:

OpenClaw 2026.3.8 and 2026.3.13 (both tested), macOS, npm install Node v24.14.0 WhatsApp channel: linked, running, connected (personal number with selfChatMode: true)

JSON · 10 lines jsonCopyCopied! "whatsapp": { "enabled": true, "dmPolicy": "allowlist", "selfChatMode": true, "allowFrom": ["+17604139426"], "groupPolicy": "open", "ackReaction": { "direct": true, "group": "always" }, "debounceMs": 0, "mediaMaxMb": 50 }

Steps to reproduce

Install OpenClaw (tested on 2026.3.8 and 2026.3.13) on macOS with a personal WhatsApp number Set channels.whatsapp.groupPolicy: "open" in ~/.openclaw/openclaw.json Confirm config is saved correctly (verify via python3 -c "import json; c=json.load(open('/Users/<user>/.openclaw/openclaw.json')); print(c['channels']['whatsapp']['groupPolicy'])" — returns "open") Restart the gateway (openclaw gateway restart) Send any message in a WhatsApp group that the linked number is a member of Check logs: tail -10 /tmp/openclaw/openclaw-$(date +%Y-%m-%d).log Observed: Message appears in logs as web-inbound, then hits applyGroupGating and is silently dropped. No agent turn triggered. No error.

Expected behavior

With groupPolicy: "open", all incoming WhatsApp group messages should bypass sender and mention gating and reach the agent.

Actual behavior

Every inbound group message is received (web-inbound logged), passes to applyGroupGating, and is silently dropped. The log ends there — no agent turn is triggered, no error, no further output. wasMentioned: false throughout.

OpenClaw version

2026.3.8 (3caab92)

Operating system

macOS 15 (arm64)

Install method

npm global (sudo npm install -g)

Model

anthropic/claude-opus-4-6

Provider / routing chain

openclaw → Anthropic API

Config file / key location

~/.openclaw/openclaw.json

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

The fix involves updating the applyGroupGating function to correctly handle the groupPolicy: "open" configuration.

  • Update the applyGroupGating function to bypass sender and mention gating when groupPolicy is set to "open":
if (config.channels.whatsapp.groupPolicy === 'open') {
  // Bypass sender and mention gating
  return true;
}
  • Add a log statement to verify that the message is not being silently dropped:
console.log('Incoming group message allowed due to open group policy');
  • Example updated applyGroupGating function:
function applyGroupGating(message, config) {
  if (config.channels.whatsapp.groupPolicy === 'open') {
    console.log('Incoming group message allowed due to open group policy');
    return true;
  }
  // Existing logic for other group policies
}

Verification

To verify that the fix worked, send a new message in a WhatsApp group that the linked number is a member of and check the logs for the Incoming group message allowed due to open group policy message. The agent turn should now be triggered correctly.

Extra Tips

  • Make sure to update the openclaw.json configuration file with the correct groupPolicy setting.
  • If issues persist, check the logs for any error messages or unexpected behavior.

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…

FAQ

Expected behavior

With groupPolicy: "open", all incoming WhatsApp group messages should bypass sender and mention gating and reach the agent.

#api#ssr#installation#tensor shape#autograd error#conversation history#tool integration#LLM response#prompt template

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix [Bug]: groupPolicy: "open" ignored — WhatsApp group messages silently dropped at applyGroupGating despite correct config [1 pull requests, 3 comments, 2 participants]