ewilliams28/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-08-28 05:16:23 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs(gateway): qualify direct-chat reply default in troubleshooting

Browse Source 
Direct chats only reply visibly when their resolved visible-reply mode is "automatic". Harnesses that set defaultVisibleReplies to "message_tool" (e.g. Codex) suppress direct-chat finals the same way as the group default, so the prior wording was misleading.
This commit is contained in:
yetval
2026-05-17 16:17:50 -04:00
parent e68b79310a
commit d116e41ffe
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/gateway/config-channels.md
+1 -1
View File
@@ -803,7 +803,7 @@ If the message tool is unavailable under the active tool policy, OpenClaw falls
Symptom: a group/channel @mention shows the typing indicator and the gateway log reports `dispatch complete (queuedFinal=false, replies=0)`, but no message lands in the room. DMs to the same agent reply normally.
Cause: the `messages.groupChat.visibleReplies` default is `"message_tool"`, so OpenClaw runs the turn but suppresses the final assistant text unless the agent calls `message(action=send)`. There is no error because suppression is the configured behavior. DMs use a different default, which is why direct chats still reply.
Cause: the `messages.groupChat.visibleReplies` default is `"message_tool"`, so OpenClaw runs the turn but suppresses the final assistant text unless the agent calls `message(action=send)`. There is no error because suppression is the configured behavior. Direct chats reply normally only when their visible-reply mode resolves to `"automatic"`; harnesses that set `defaultVisibleReplies: "message_tool"` (for example, the Codex harness) suppress direct-chat finals the same way.
Fix: either pick a stronger tool-calling model, or set `messages.groupChat.visibleReplies: "automatic"` to restore legacy visible replies. The gateway hot-reloads `messages` config after the file is saved; only restart the gateway when file watching or config reload is disabled in the deployment.