feat(channels): add neverReply config for group message suppression by cayde-6 · Pull Request #42400 · openclaw/openclaw

cayde-6 · 2026-03-10T17:28:40Z

Summary

Adds neverReply: boolean config option to all 15 group-capable channels. When enabled, group messages pass access control and are recorded as pending history context, but no LLM call is made and no reply is sent. DMs continue to work normally.

Use case: monitoring many group chats (work, school, client) for context accumulation with zero outbound risk.

Difference from groupPolicy: "disabled": disabled drops messages before history; neverReply: true lets them through access control and records them — the bot just never replies.

Quick start

```yaml
channels:
telegram:
groupPolicy: open
neverReply: true # observe all Telegram groups silently
defaults:
neverReply: true # or silence all channels at once
```

Config resolution: account-level → channel-level → channels.defaults.neverReply.

Changes

Core: resolveNeverReply() in src/config/group-policy.ts, re-exported via src/plugin-sdk/channel-policy
Config schemas: neverReply: z.boolean().optional() added to all 15 channel schemas (core providers schema + extension schemas for line, matrix, mattermost, bluebubbles, zalo, zalouser)
Channel handlers (15): neverReply check after group access control in telegram, whatsapp, signal, slack, imessage, googlechat, irc, matrix, mattermost, msteams, bluebubbles, discord, line, zalo, zalouser
Generated schema: src/config/schema.base.generated.ts regenerated
Help/labels: channels.defaults.neverReply in schema.help.ts and schema.labels.ts
Docs: new ## Silent observation (neverReply) section in docs/channels/groups.md, updated quick-flow diagram and use-case table
Changelog: entry under Unreleased

Compatibility

Backward compatible — neverReply defaults to undefined/false, no existing behavior changes
No migration needed
No new network calls, secrets handling, or attack surface

Linked

Related Feature request: Listen-only / suppress-outbound channel mode for WhatsApp #22791 (listen-only / suppress-outbound for WhatsApp)
Related [Feature] Native listen-only mode: receive all messages without LLM invocation #15268 (native listen-only mode)
Related [Feature Request] Group pairing flow: notify owner + read-only mode for unconfigured groups #11489 (group pairing + read-only mode)

greptile-apps · 2026-03-10T17:35:34Z

Greptile Summary

This PR adds a neverReply boolean config option across all 14 group-capable channels. When enabled, the bot passively records group messages into pending history but never triggers an LLM run or sends a reply; DMs are unaffected. The implementation follows the established groupPolicy / requireMention ordering (disabled → allowlist gating → neverReply → mention gating → reply), and the config cascade (account > channel > defaults) is correctly implemented via the new resolveNeverReply helper.

All issues flagged in previous review rounds (history not recorded in 6 channels, Line and IRC missing implementations, MSTeams/WhatsApp accountId not threaded, Mattermost/ZaloUser write-key ≠ read-key, GoogleChat wall-clock timestamp) have been successfully addressed in this revision. The core feature is complete, well-tested, and backward-compatible.

Confidence Score: 5/5

Safe to merge—all critical issues from prior reviews have been resolved. The feature is backward-compatible and well-tested.
All previously flagged issues have been verified as fixed: history is properly recorded in all 14 channels (including the 6 that had missing calls), Line and IRC have complete implementations with account-scoped history keys, Mattermost and ZaloUser use consistent write/read keys, MSTeams/WhatsApp properly thread accountId, and GoogleChat uses correct event timestamps. The config cascade is properly implemented, DMs are unaffected, and the feature defaults to false for backward compatibility. The codebase passes 873 tests with 0 failures.
No files require special attention. All channel implementations are consistent and correct.

_{Last reviewed commit: fe0af6d}

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1f77feb06a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

cayde-6 · 2026-03-10T18:06:53Z

All review findings from Greptile and Codex have been addressed in commit 54a04e1:

1. History recording added to 6 extension channels (BlueBubbles, Mattermost, GoogleChat, Matrix, Zalo, ZaloUser)

Each now calls recordPendingHistoryEntryIfEnabled before the early return, matching the pattern used in built-in channels

2. Line monitor implementation added

Was config-only stub; now has a proper resolveNeverReply check with early return in src/line/monitor.ts

3. accountId passed everywhere

Discord: uses resolvedAccountId (from params.accountId ?? DEFAULT_ACCOUNT_ID)
MSTeams: uses DEFAULT_ACCOUNT_ID (neverReply check happens before route resolution)
WhatsApp: added accountId to ApplyGroupGatingParams, passed from route.accountId in caller

All 14 channels now consistently: pass accountId, record pending history, and log the drop.

Full test suite passes: 873 files, 7113 tests, 0 failures.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 54a04e1365

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

cayde-6 · 2026-03-10T18:17:33Z

@greptile review
@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 54a04e1365

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ed8b90a551

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f150a378c9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

cayde-6 · 2026-03-10T19:37:42Z

@greptile-apps review

All review comments have been addressed:

Google Chat, Matrix, Zalo: wired up buildPendingHistoryContextFromMap so recorded history is consumed
Line: moved neverReply check to bot-handlers.ts for proper history recording
IRC: added neverReply implementation
Discord, MSTeams, WhatsApp: added accountId to resolveNeverReply calls
BlueBubbles, Mattermost, ZaloUser: added recordPendingHistoryEntryIfEnabled before early returns

cayde-6 · 2026-03-10T19:37:44Z

@chatgpt-codex-connector review

All review comments have been addressed — see replies on each thread.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f150a378c9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Add a `neverReply` config option to all 15 group-capable channels (bluebubbles, discord, googlechat, imessage, irc, line, matrix, mattermost, msteams, signal, slack, telegram, whatsapp, zalo, zalouser). When enabled, group messages pass access control and are recorded as pending history context where infrastructure exists, but no LLM call or reply is made. DMs continue to flow normally. Resolution follows the standard account → channel → defaults precedence via `resolveNeverReply` in `src/config/group-policy.ts`, exported from the `openclaw/plugin-sdk/channel-policy` SDK seam. Channels with group history infrastructure (telegram, signal, slack, discord, irc, line, matrix, mattermost, msteams, whatsapp, imessage, bluebubbles, zalouser) record the silenced message via `recordPendingHistoryEntryIfEnabled` so it remains available as context for future replies. Channels without history infrastructure (zalo, googlechat) drop the message silently with a clear log message. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Verifies for each group-capable channel that: - the channel's integration source imports `resolveNeverReply` from `openclaw/plugin-sdk/channel-policy`, - the call site passes the matching channel name string, - the call is reachable only on a group code path (DMs unaffected), - accountId is threaded into the resolver call. Also covers the four-step precedence of `resolveNeverReply` (account override > channel value > channels.defaults > false fallback) so schema/wiring drift surfaces as a single localized failure instead of silently breaking observation across one channel. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

The opengrep precise scan flags enqueueSystemEvent calls with interpolated text without explicit trust. The default is trusted: true; mark it explicitly to self-document intent and pass the changed-files scan.

Discord, LINE, and Mattermost neverReply branches were returning before the existing pending-history record paths ran, so suppressed group messages were dropped instead of preserved as context. Record the pending entry alongside the existing skip paths before returning.

- matrix: move neverReply check after access-state evaluation and pending-history text computation; record pending entry before returning so silent rooms still preserve context. - irc: accept channels.irc.neverReply in the strict account/channel schema (runtime already reads it). - slack: include file placeholder fallback in neverReply pending history so file-only messages survive silent mode. - telegram: drop inert neverReply from group/topic schemas (resolver only handles account/channel/defaults). - regen config-baseline and plugin-sdk-api-baseline.

cayde-6 · 2026-05-05T12:38:01Z

Closing this — the use case is already covered by the existing listen-only plugin without any core changes:

Plugin: https://github.com/flowolforg/openclaw-listen-only
Hook: before_dispatch (Plugins: add a before-dispatch hook to the reply pipeline #50444), merged March 2026, specifically designed for listen-only / spam-filter / rate-limiter use cases.

Maintainer direction in #71988: inbound_claim stays plugin-bound by design; broadcast/listen-only behavior belongs in plugins via before_dispatch, not in core config. A 15-channel core knob is the wrong architectural layer.

Thanks to everyone who reviewed — @greptile-apps, @chatgpt-codex-connector, @clawsweeper, @flowolforg, @Michiel-claw. Closing in favor of the plugin path.

chatgpt-codex-connector · 2026-05-05T12:38:13Z

To use Codex here, create an environment for this repo.

greptile-apps Bot reviewed Mar 10, 2026

View reviewed changes

Comment thread extensions/bluebubbles/src/monitor-processing.ts

Comment thread src/line/config-schema.ts

Comment thread extensions/msteams/src/monitor-handler/message-handler.ts Outdated

chatgpt-codex-connector Bot reviewed Mar 10, 2026

View reviewed changes

Comment thread src/config/zod-schema.providers-core.ts

Comment thread extensions/googlechat/src/monitor-access.ts Outdated

greptile-apps Bot reviewed Mar 10, 2026

View reviewed changes

Comment thread src/line/monitor.ts Outdated

Comment thread src/config/zod-schema.providers-core.ts

chatgpt-codex-connector Bot reviewed Mar 10, 2026

View reviewed changes

Comment thread src/line/monitor.ts Outdated

Comment thread extensions/googlechat/src/monitor-access.ts Outdated

openclaw-barnacle Bot added the channel: irc label Mar 10, 2026

chatgpt-codex-connector Bot reviewed Mar 10, 2026

View reviewed changes

Comment thread extensions/matrix/src/matrix/monitor/handler.ts Outdated

Comment thread extensions/zalo/src/monitor.ts Outdated

chatgpt-codex-connector Bot reviewed Mar 10, 2026

View reviewed changes

Comment thread extensions/googlechat/src/monitor-access.ts Outdated

Comment thread extensions/matrix/src/matrix/monitor/handler.ts Outdated

Comment thread extensions/zalo/src/monitor.ts Outdated

greptile-apps Bot reviewed Mar 10, 2026

View reviewed changes

Comment thread extensions/irc/src/inbound.ts

Comment thread extensions/googlechat/src/monitor-access.ts Outdated

chatgpt-codex-connector Bot reviewed Mar 10, 2026

View reviewed changes

Comment thread extensions/googlechat/src/monitor-access.ts Outdated

Comment thread extensions/matrix/src/matrix/monitor/handler.ts Outdated

cayde-6 force-pushed the feat/never-reply-group-policy branch 2 times, most recently from 0bf595b to 67a9bd7 Compare April 28, 2026 16:17

openclaw-barnacle Bot added commands Command implementations size: L and removed size: M labels Apr 28, 2026

cayde-6 force-pushed the feat/never-reply-group-policy branch 6 times, most recently from 5e92ba0 to a11d39d Compare April 28, 2026 22:13

BradGroux mentioned this pull request Apr 29, 2026

WORKING: All Microsoft Issues and PRs (refresh) #74163

Draft

cayde-6 force-pushed the feat/never-reply-group-policy branch 2 times, most recently from 84e61ac to 8e09c54 Compare April 29, 2026 08:21

openclaw-barnacle Bot added size: M and removed commands Command implementations size: L labels Apr 29, 2026

cayde-6 force-pushed the feat/never-reply-group-policy branch 2 times, most recently from 436e391 to a2e7ca3 Compare April 29, 2026 09:39

openclaw-barnacle Bot added size: L and removed size: M labels Apr 29, 2026

cayde-6 force-pushed the feat/never-reply-group-policy branch from a2e7ca3 to e17f91f Compare April 30, 2026 23:20

openclaw-barnacle Bot added the triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. label May 5, 2026

cayde-6 and others added 5 commits May 5, 2026 12:27

fix(discord): mark system-event text as explicitly trusted

b04a0aa

The opengrep precise scan flags enqueueSystemEvent calls with interpolated text without explicit trust. The default is trusted: true; mark it explicitly to self-document intent and pass the changed-files scan.

Uh oh!

Conversation

cayde-6 commented Mar 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Quick start

Changes

Compatibility

Linked

Uh oh!

greptile-apps Bot commented Mar 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 5/5

Uh oh!

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

cayde-6 commented Mar 10, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

cayde-6 commented Mar 10, 2026

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

cayde-6 commented Mar 10, 2026

Uh oh!

cayde-6 commented Mar 10, 2026

Uh oh!

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

cayde-6 commented May 5, 2026

Uh oh!

chatgpt-codex-connector Bot commented May 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

cayde-6 commented Mar 10, 2026 •

edited

Loading

greptile-apps Bot commented Mar 10, 2026 •

edited

Loading