chore(sync): mirror docs from openclaw/openclaw@97e2f5b332

This commit is contained in:
openclaw-docs-sync[bot] 2026-04-29 19:05:27 +00:00
parent 610f200b8f
commit 046f5fb880
2 changed files with 3 additions and 3 deletions

View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "e69da9d5781c0f60ee10ffcec6aa78e1994a416c",
"syncedAt": "2026-04-29T18:55:20.228Z"
"sha": "97e2f5b3324bd825aa307c94b97a9b7c45cab4af",
"syncedAt": "2026-04-29T19:03:45.976Z"
}

View File

@ -329,7 +329,7 @@ Replying to a bot message counts as an implicit mention when the channel support
- 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.
- Groups where silent replies are allowed treat clean empty or reasoning-only model turns as silent, equivalent to `NO_REPLY`. Direct chats do the same only when direct silent replies are explicitly allowed; otherwise empty replies remain failed agent turns.
- 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.<channel>.historyLimit` (or `channels.<channel>.accounts.*.historyLimit`) for overrides. Set `0` to disable.