diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 7f1c87a32..58cc1db7a 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "ccfa0c19641a76f8a80987865cd8e8c4b589b2c0", - "syncedAt": "2026-04-27T22:31:55.799Z" + "sha": "496a5eb56f466e828e7f843a0a55dfc7fbe01199", + "syncedAt": "2026-04-27T22:32:18.241Z" } diff --git a/docs/channels/groups.md b/docs/channels/groups.md index 2ac65b91d..5022f94f4 100644 --- a/docs/channels/groups.md +++ b/docs/channels/groups.md @@ -289,6 +289,7 @@ Replying to a bot message counts as an implicit mention when the channel support - Surfaces that provide explicit mentions still pass; patterns are a fallback. - Per-agent override: `agents.list[].groupChat.mentionPatterns` (useful when multiple agents share a group). - Mention gating is only enforced when mention detection is possible (native mentions or `mentionPatterns` are configured). + - Group chat prompt context carries the resolved silent-reply instruction every turn; workspace files should not duplicate `NO_REPLY` mechanics. - Groups where silent replies are allowed treat clean empty or reasoning-only model turns as silent, equivalent to `NO_REPLY`. Direct chats still treat empty replies as a failed agent turn. - Discord defaults live in `channels.discord.guilds."*"` (overridable per guild/channel). - Group history context is wrapped uniformly across channels and is **pending-only** (messages skipped due to mention gating); use `messages.groupChat.historyLimit` for the global default and `channels..historyLimit` (or `channels..accounts.*.historyLimit`) for overrides. Set `0` to disable. diff --git a/docs/concepts/system-prompt.md b/docs/concepts/system-prompt.md index 5c9acd520..35abeb9db 100644 --- a/docs/concepts/system-prompt.md +++ b/docs/concepts/system-prompt.md @@ -96,6 +96,11 @@ OpenClaw can render smaller system prompts for sub-agents. The runtime sets a When `promptMode=minimal`, extra injected prompts are labeled **Subagent Context** instead of **Group Chat Context**. +For channel auto-reply runs, OpenClaw can omit the generic **Silent Replies** +section when the direct/group chat context already includes the resolved +conversation-specific `NO_REPLY` behavior. This avoids repeating token mechanics +in both the global system prompt and channel context. + ## Workspace bootstrap injection Bootstrap files are trimmed and appended under **Project Context** so the model sees identity and profile context without needing explicit reads: diff --git a/docs/reference/templates/AGENTS.md b/docs/reference/templates/AGENTS.md index 9b3899fc5..d2053ebb5 100644 --- a/docs/reference/templates/AGENTS.md +++ b/docs/reference/templates/AGENTS.md @@ -94,7 +94,7 @@ In group chats where you receive every message, be **smart about when to contrib - Correcting important misinformation - Summarizing when asked -**Stay silent (HEARTBEAT_OK) when:** +**Stay silent when:** - It's just casual banter between humans - Someone already answered the question