- Codex app-server: preserve network access for sandboxed Codex code-mode turns when the OpenClaw sandbox allows outbound egress. Fixes #83347. Thanks @YusukeIt0.

- QA-Lab: keep the OTLP smoke decoder independent of removed OpenTelemetry generated-root internals.

- Messages: default group/channel visible replies to automatic final delivery again, keeping `message_tool` opt-in for ambient/shared rooms and tool-reliable models.

- Agents/code mode: preserve agent, session, run, and channel context in `before_tool_call` hooks for top-level `exec`/`wait` dispatches. Fixes #83387.

- Replies: keep final payload delivery after live preview updates so channels can finalize or send the completed answer instead of losing preview-only drafts. (#83468)

- Discord: deliver final replies in progress-mode preview streams instead of deduplicating the final visible message. (#83443) Thanks @compoodment.

## Visible reply modes

`messages.groupChat.visibleReplies: "message_tool"` is the recommended group and channel default. It lets the agent decide when to speak by calling the message tool. If the model returns final text without calling the tool, OpenClaw keeps that final text private and logs suppressed delivery metadata.

`messages.groupChat.visibleReplies` defaults to `"automatic"` for normal group/channel user requests. Keep that default when you want final assistant text to post visibly without requiring an explicit message-tool call.

Use `messages.groupChat.visibleReplies: "automatic"` only when you want legacy behavior where normal group requests post final assistant text automatically.

For ambient always-on rooms, `messages.groupChat.visibleReplies: "message_tool"` is still recommended, especially with latest-generation, tool-reliable models such as GPT 5.5. It lets the agent decide when to speak by calling the message tool. If the model returns final text without calling the tool, OpenClaw keeps that final text private and logs suppressed delivery metadata.

Room events stay strict even when other group requests use automatic replies. Unmentioned ambient room events still require `message(action=send)` for visible output.

2. Confirm `requireMention: false` is set at the room level you expect.

3. Check whether `messages.groupChat.unmentionedInbound` or the agent override is `"room_event"`.

4. Inspect logs for suppressed final payload metadata or `didSendViaMessagingTool: false`.

5. Use a model/runtime that reliably calls tools, or set `messages.groupChat.visibleReplies: "automatic"` for legacy final replies on normal group requests.

5. For normal group requests, keep or restore `messages.groupChat.visibleReplies: "automatic"` if you want final replies posted automatically. For ambient rooms using `message_tool`, use a model/runtime that reliably calls tools.

If Telegram ambient rooms do not trigger at all, check BotFather privacy mode and verify the Gateway is receiving normal group messages.

<Step title="Allow responses without @mention">

By default, your agent only responds in guild channels when @mentioned. For a private server, you probably want it to respond to every message.

In guild channels, visible Discord output should use the `message` tool by default, so the agent can lurk and only post when it decides a channel reply is useful. Ambient room events stay quiet unless the tool sends. See [Ambient room events](/channels/ambient-room-events) for the full lurk-mode config.

In guild channels, normal replies post automatically by default. For shared always-on rooms, opt into `messages.groupChat.visibleReplies: "message_tool"` so the agent can lurk and only post when it decides a channel reply is useful. This works best with latest-generation, tool-reliable models such as GPT 5.5. Ambient room events stay quiet unless the tool sends. See [Ambient room events](/channels/ambient-room-events) for the full lurk-mode config.

This means the selected model should reliably call tools. If Discord shows typing and the logs show token usage but no posted message, check whether the turn was configured as an ambient room event or use the config below to restore legacy automatic final replies for normal group requests.

If Discord shows typing and the logs show token usage but no posted message, check whether the turn was configured as an ambient room event or opted into message-tool visible replies.

<Tabs>

<Tab title="Ask your agent">

}

```

To restore legacy automatic final replies for group/channel rooms, set `messages.groupChat.visibleReplies: "automatic"`.

To require message-tool sends for visible group/channel replies, set `messages.groupChat.visibleReplies: "message_tool"`.

</Tab>

</Tabs>

- Heartbeats are intentionally skipped for groups to avoid noisy broadcasts.

- Echo suppression uses the combined batch string; if you send identical text twice without mentions, only the first will get a response.

- Session store entries will appear as `agent:<agentId>:whatsapp:group:<jid>` in the session store (`~/.openclaw/agents/<agentId>/sessions/sessions.json` by default); a missing entry just means the group hasn't triggered a run yet.

- Typing indicators in groups follow `agents.defaults.typingMode`. When visible replies use the default message-tool-only mode, typing starts immediately by default so group members can see the agent is working even if no automatic final reply is posted. Explicit typing-mode config still wins.

- Typing indicators in groups follow `agents.defaults.typingMode`. When visible replies are opted into message-tool-only mode, typing starts immediately by default so group members can see the agent is working even if no automatic final reply is posted. Explicit typing-mode config still wins.

## Related

## Visible replies

For group/channel rooms, OpenClaw defaults to `messages.groupChat.visibleReplies: "message_tool"`.

`openclaw doctor --fix` writes this default into configured-channel configs that omit it.

That means the agent still processes the turn and can update memory/session state, and it should speak visibly with `message(action=send)` when it has a room reply. If the model misses that tool and returns substantive final text, OpenClaw keeps that final text private instead of posting it to the room.

This default depends on a model/runtime that reliably calls tools. If logs show

assistant text but `didSendViaMessagingTool: false`, the model answered

privately instead of calling the message tool. The room stays silent, and the

gateway verbose log records the suppressed final payload metadata. That is not

a Discord/Slack/Telegram send failure, but a tool-discipline signal. Use a

tool-call-reliable model for group/channel sessions, or set

`messages.groupChat.visibleReplies: "automatic"` when you want all visible group

replies to use the legacy final-reply path.

For normal group/channel requests, OpenClaw defaults to `messages.groupChat.visibleReplies: "automatic"`. Final assistant text posts through the legacy visible reply path unless you opt the room into message-tool-only output.

Use `messages.groupChat.visibleReplies: "message_tool"` when a shared room should let the agent decide when to speak by calling `message(action=send)`. This works best for group rooms backed by latest-generation, tool-reliable models such as GPT 5.5. If the model misses that tool and returns substantive final text, OpenClaw keeps that final text private instead of posting it to the room.

If the message tool is unavailable under the active tool policy, OpenClaw falls

back to automatic visible replies instead of silently suppressing the response.

Mentioned messages, commands, abort requests, and DMs stay user requests.

To restore legacy automatic final replies for group/channel requests:

To require visible output to go through the message tool for group/channel requests:

```json5

{

messages: {

groupChat: {

visibleReplies: "automatic",

visibleReplies: "message_tool",

},

},

}

- channel allowlist (`channels.slack.channels`) — **keys must be channel IDs** (`C12345678`), not names (`#channel-name`). Name-based keys silently fail under `groupPolicy: "allowlist"` because channel routing is ID-first by default. To find an ID: right-click the channel in Slack → **Copy link** — the `C...` value at the end of the URL is the channel ID.

- `requireMention`

- per-channel `users` allowlist

- `messages.groupChat.visibleReplies`: if it is `"message_tool"` and logs show assistant text with no `message(action=send)` call, the model missed the visible message-tool path. Final text stays private in this mode; inspect the gateway verbose log for suppressed payload metadata, or set it to `"automatic"` if you want every normal assistant final reply posted through the legacy path.

- `messages.groupChat.visibleReplies`: normal group/channel requests default to `"automatic"`. If you opted into `"message_tool"` and logs show assistant text with no `message(action=send)` call, the model missed the visible message-tool path. Final text stays private in this mode; inspect the gateway verbose log for suppressed payload metadata, or set it to `"automatic"` if you want every normal assistant final reply posted through the legacy path.

- `messages.groupChat.unmentionedInbound`: if it is `"room_event"`, unmentioned allowed channel chatter is ambient context and stays silent unless the agent calls the `message` tool. See [Ambient room events](/channels/ambient-room-events).

```json5

### Discord failure signatures

| Symptom | Fastest check | Fix |

| ----------------------------------------- | ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

| Bot online but no guild replies | `openclaw channels status --probe` | Allow guild/channel and verify message content intent. |

| Group messages ignored | Check logs for mention gating drops | Mention bot or set guild/channel `requireMention: false`. |

| Typing/token usage but no Discord message | Check whether this is an ambient room event or a missed `message(action=send)` call | Inspect the gateway verbose log for suppressed final payload metadata, verify `messages.groupChat.unmentionedInbound`, read [Ambient room events](/channels/ambient-room-events), or set `messages.groupChat.visibleReplies: "automatic"` to use the legacy final-reply path for normal group requests. |

| DM replies missing | `openclaw pairing list discord` | Approve DM pairing or adjust DM policy. |

| Symptom | Fastest check | Fix |

| ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

| Bot online but no guild replies | `openclaw channels status --probe` | Allow guild/channel and verify message content intent. |

| Group messages ignored | Check logs for mention gating drops | Mention bot or set guild/channel `requireMention: false`. |

| Typing/token usage but no Discord message | Check whether this is an ambient room event or an opted-in `message_tool` room where the model missed `message(action=send)` | Inspect the gateway verbose log for suppressed final payload metadata, verify `messages.groupChat.unmentionedInbound`, read [Ambient room events](/channels/ambient-room-events), or keep `messages.groupChat.visibleReplies: "automatic"` for normal group requests. |

| DM replies missing | `openclaw pairing list discord` | Approve DM pairing or adjust DM policy. |

Full troubleshooting: [Discord troubleshooting](/channels/discord#troubleshooting)

Group messages default to **require mention** (metadata mention or safe regex patterns). Applies to WhatsApp, Telegram, Discord, Google Chat, and iMessage group chats.

Visible replies are controlled separately. Group/channel rooms default to `messages.groupChat.visibleReplies: "message_tool"`: OpenClaw still processes the turn and asks the agent to use `message(action=send)` for visible room output. If the model returns final text without calling the message tool, that final text stays private and the gateway verbose log records suppressed payload metadata. Set `"automatic"` when you want all visible group replies to use the legacy final-reply path. To apply the same tool-only visible-reply behavior to direct chats too, set `messages.visibleReplies: "message_tool"`; the Codex harness also uses that tool-only behavior as its unset direct-chat default.

Visible replies are controlled separately. Normal group/channel requests default to `messages.groupChat.visibleReplies: "automatic"`: final assistant text posts through the legacy visible reply path. Set `"message_tool"` when a shared room should only post visible output after the agent calls `message(action=send)`. If the model returns final text without calling the message tool, that final text stays private and the gateway verbose log records suppressed payload metadata. To apply the same tool-only visible-reply behavior to direct chats too, set `messages.visibleReplies: "message_tool"`; the Codex harness also uses that tool-only behavior as its unset direct-chat default.

Tool-only visible replies require a model/runtime that reliably calls tools. If

Tool-only visible replies require a model/runtime that reliably calls tools, and are recommended for shared ambient rooms on latest-generation models such as GPT 5.5. If

the session log shows assistant text with `didSendViaMessagingTool: false`, the

model produced private final text instead of calling the message tool. Switch

to a stronger tool-calling model for that channel, inspect the gateway verbose

log for the suppressed payload summary, or set

`messages.groupChat.visibleReplies: "automatic"` to use legacy visible final

replies for every group/channel request.

`messages.groupChat.visibleReplies: "automatic"` to use visible final replies

for every group/channel request.

If the message tool is unavailable under the active tool policy, OpenClaw falls back to automatic visible replies instead of silently suppressing the response. `openclaw doctor` warns about this mismatch.

groupChat: {

historyLimit: 50,

unmentionedInbound: "room_event", // always-on unmentioned room chatter becomes quiet context

visibleReplies: "message_tool", // default; use "automatic" for legacy final replies

visibleReplies: "message_tool", // opt-in; require message(action=send) for visible room replies

},

},

agents: {

messages: {

visibleReplies: "automatic",

groupChat: {

visibleReplies: "message_tool", // default; visible output requires message(action=send)

visibleReplies: "message_tool", // opt-in; visible output requires message(action=send)

unmentionedInbound: "room_event",

},

},

ackReactionScope: "group-mentions",

groupChat: {

historyLimit: 50,

visibleReplies: "message_tool", // prefer message tool; final text falls back for normal requests

visibleReplies: "message_tool", // opt in for shared rooms with tool-reliable models

unmentionedInbound: "room_event",

},

queue: {