## Ack reactions

`ackReaction` sends an acknowledgement emoji while OpenClaw is processing an inbound message.

`ackReaction` sends an acknowledgement emoji while OpenClaw is processing an inbound message. `ackReactionScope` decides _when_ that emoji is actually sent.

### Emoji (`ackReaction`)

Resolution order:

- `channels.slack.accounts.<accountId>.ackReaction`

- `channels.slack.ackReaction`

- `messages.ackReaction`

- agent identity emoji fallback (`agents.list[].identity.emoji`, else "👀")

- agent identity emoji fallback (`agents.list[].identity.emoji`, else `"eyes"` / 👀)

Notes:

- Slack expects shortcodes (for example `"eyes"`).

- Use `""` to disable the reaction for the Slack account or globally.

### Scope (`messages.ackReactionScope`)

The Slack provider reads scope from `messages.ackReactionScope` (default `"group-mentions"`). There is no Slack-account or Slack-channel-level override today; the value is global to the gateway.

Values:

- `"all"`: react in DMs and groups.

- `"direct"`: react in DMs only.

- `"group-all"`: react on every group message (no DMs).

- `"group-mentions"` (default): react in groups, but only when the bot is mentioned (or in group mentionables that opted in). **DMs are excluded.**

- `"off"` / `"none"`: never react.

<Note>

The default scope (`"group-mentions"`) does not fire ack reactions in direct messages. To see the configured `ackReaction` (for example `"eyes"`) on inbound Slack DMs, set `messages.ackReactionScope` to `"direct"` or `"all"`. `messages.ackReactionScope` is read at Slack provider startup, so a gateway restart is needed for the change to take effect.

</Note>

```json5

{

messages: {

ackReaction: "eyes",

ackReactionScope: "all", // react in DMs and groups

},

}

```

## Text streaming

`channels.slack.streaming` controls live preview behavior:

</Accordion>

<Accordion title="Ack reactions">

`ackReaction` sends an acknowledgement emoji while OpenClaw is processing an inbound message.

`ackReaction` sends an acknowledgement emoji while OpenClaw is processing an inbound message. `ackReactionScope` decides *when* that emoji is actually sent.

Resolution order:

**Emoji (`ackReaction`) resolution order:**

- `channels.telegram.accounts.<accountId>.ackReaction`

- `channels.telegram.ackReaction`

- Telegram expects unicode emoji (for example "👀").

- Use `""` to disable the reaction for a channel or account.

**Scope (`messages.ackReactionScope`):**

The Telegram provider reads scope from `messages.ackReactionScope` (default `"group-mentions"`). There is no Telegram-account or Telegram-channel-level override today.

Values: `"all"` (DMs + groups), `"direct"` (DMs only), `"group-all"` (every group message, no DMs), `"group-mentions"` (groups when the bot is mentioned; **no DMs** — this is the default), `"off"` / `"none"` (disabled).

<Note>

The default scope (`"group-mentions"`) does not fire ack reactions in direct messages. To get an ack reaction on inbound Telegram DMs, set `messages.ackReactionScope` to `"direct"` or `"all"`. The value is read at Telegram provider startup, so a gateway restart is needed for the change to take effect.

</Note>

</Accordion>

<Accordion title="Config writes from Telegram events and commands">