Signal 群聊不触发的实操修复：为 channels.signal.groups 增加 schema 支持

问题/场景：Signal 群消息被 mention gating 静默忽略，配置 `channels.signal.groups` 却报 `Unrecognized key: groups`。前置条件：已接入 Signal 且有配置文件修改权限。实施步骤：升级到包含 PR #20409 的版本→在 account 或全局层声明 groups→按群设置 `requireMention`/`tools`。关键配置：`groups.<groupId>.requireMention: false`。验证：群内不 @ 机器人也能按规则处理。风险：放宽 mention 门槛会提高误触发概率。

GITHUBDiscovered 2026-02-19Author unisone

Prerequisites

Signal channel is already connected, and you can edit OpenClaw config plus restart gateway.
Runtime version should include PR #20409 (or later commit with signal groups schema).

Steps

Confirm current behavior: config validation rejects `channels.signal.groups` with unknown key error.
Upgrade OpenClaw build to include the schema fix, then restart gateway.
Add `groups` map under `channels.signal` (global or per-account) and set `requireMention` by group risk level.
Optionally scope tools per group with `tools`/`toolsBySender` to avoid over-privileged execution.
Send non-mention and mention test messages in target Signal groups and compare handling results.

Commands

openclaw gateway status

openclaw gateway restart

openclaw help

Verify

Gateway accepts config with `channels.signal.groups`, and target groups process messages according to `requireMention` policy instead of silently dropping.

Caveats

Signal has no native @mention semantics equivalent to some channels; false positives/negatives in mention policy should be tested per group（需验证）.
Disabling mention requirement in noisy groups may increase tool-call volume and operational risk.

Source attribution

This tip is aggregated from community/public sources and preserved with attribution.

Open original source ↗

Visit original post