Skip to content

Commit f4129cd

Browse files
vincentkocvincentkoc
committed
docs(channels): batch convert prose callouts to Mintlify components
- msteams: 5 callouts (Note/Warning) for preview status, devtunnel auth, group policy, multi-tenant deprecation, user-prefix targeting - slack: replyToMode threading note - whatsapp: dms vs direct prompt override note - group-messages: mentionPatterns cross-channel note - signal: signal-cli main session de-auth warning
1 parent 6908bd3 commit f4129cd

5 files changed

Lines changed: 27 additions & 9 deletions

File tree

‎docs/channels/group-messages.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,9 @@ title: "Group messages"
77

88
Goal: let Clawd sit in WhatsApp groups, wake up only when pinged, and keep that thread separate from the personal DM session.
99

10-
Note: `agents.list[].groupChat.mentionPatterns` is now used by Telegram/Discord/Slack/iMessage as well; this doc focuses on WhatsApp-specific behavior. For multi-agent setups, set `agents.list[].groupChat.mentionPatterns` per agent (or use `messages.groupChat.mentionPatterns` as a global fallback).
10+
<Note>
11+
`agents.list[].groupChat.mentionPatterns` is also used by Telegram, Discord, Slack, and iMessage. This doc focuses on WhatsApp-specific behavior. For multi-agent setups, set `agents.list[].groupChat.mentionPatterns` per agent, or use `messages.groupChat.mentionPatterns` as a global fallback.
12+
</Note>
1113

1214
## Current implementation (2025-12-03)
1315

‎docs/channels/msteams.md‎

Lines changed: 15 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,9 @@ teams login
3939
teams status # verify you're logged in and see your tenant info
4040
```
4141

42-
> **Note:** The Teams CLI is currently in preview. Commands and flags may change between releases.
42+
<Note>
43+
The Teams CLI is currently in preview. Commands and flags may change between releases.
44+
</Note>
4345

4446
**2. Start a tunnel** (Teams can't reach localhost)
4547

@@ -55,7 +57,9 @@ devtunnel host my-openclaw-bot
5557
# Your endpoint: https://<tunnel-id>.devtunnels.ms/api/messages
5658
```
5759

58-
> **Note:** `--allow-anonymous` is required because Teams can't authenticate with devtunnels. Each incoming bot request is still validated by the Teams SDK automatically.
60+
<Note>
61+
`--allow-anonymous` is required because Teams cannot authenticate with devtunnels. Each incoming bot request is still validated by the Teams SDK automatically.
62+
</Note>
5963

6064
Alternatives: `ngrok http 3978` or `tailscale funnel 3978` (but these may change URLs each session).
6165

@@ -112,7 +116,9 @@ This runs diagnostics across bot registration, AAD app config, manifest validity
112116

113117
For production deployments, consider using [federated authentication](#federated-authentication-certificate--managed-identity) (certificate or managed identity) instead of client secrets.
114118

115-
Note: group chats are blocked by default (`channels.msteams.groupPolicy: "allowlist"`). To allow group replies, set `channels.msteams.groupAllowFrom` (or use `groupPolicy: "open"` to allow any member, mention-gated).
119+
<Note>
120+
Group chats are blocked by default (`channels.msteams.groupPolicy: "allowlist"`). To allow group replies, set `channels.msteams.groupAllowFrom`, or use `groupPolicy: "open"` to allow any member (mention-gated).
121+
</Note>
116122

117123
## Goals
118124

@@ -217,7 +223,9 @@ If you can't use the Teams CLI, you can set up the bot manually through the Azur
217223
| **Type of App** | **Single Tenant** (recommended - see note below) |
218224
| **Creation type** | **Create new Microsoft App ID** |
219225

220-
> **Deprecation notice:** Creation of new multi-tenant bots was deprecated after 2025-07-31. Use **Single Tenant** for new bots.
226+
<Warning>
227+
Creation of new multi-tenant bots was deprecated after 2025-07-31. Use **Single Tenant** for new bots.
228+
</Warning>
221229

222230
3. Click **Review + create** → **Create** (wait ~1-2 minutes)
223231

@@ -914,7 +922,9 @@ openclaw message send --channel msteams --target "conversation:19:abc...@thread.
914922
}
915923
```
916924

917-
Note: Without the `user:` prefix, names default to group/team resolution. Always use `user:` when targeting people by display name.
925+
<Note>
926+
Without the `user:` prefix, names default to group or team resolution. Always use `user:` when targeting people by display name.
927+
</Note>
918928

919929
## Proactive messaging
920930

‎docs/channels/signal.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -152,7 +152,9 @@ openclaw channels status --probe
152152
- Approve code on the server: `openclaw pairing approve signal <PAIRING_CODE>`.
153153
- Save the bot number as a contact on your phone to avoid "Unknown contact".
154154

155-
Important: registering a phone number account with `signal-cli` can de-authenticate the main Signal app session for that number. Prefer a dedicated bot number, or use QR link mode if you need to keep your existing phone app setup.
155+
<Warning>
156+
Registering a phone number account with `signal-cli` can de-authenticate the main Signal app session for that number. Prefer a dedicated bot number, or use QR link mode if you need to keep your existing phone app setup.
157+
</Warning>
156158

157159
Upstream references:
158160

‎docs/channels/slack.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -530,7 +530,9 @@ Manual reply tags are supported:
530530
- `[[reply_to_current]]`
531531
- `[[reply_to:<id>]]`
532532

533-
Note: `replyToMode="off"` disables **all** reply threading in Slack, including explicit `[[reply_to_*]]` tags. This differs from Telegram, where explicit tags are still honored in `"off"` mode — Slack threads hide messages from the channel while Telegram replies stay visible inline.
533+
<Note>
534+
`replyToMode="off"` disables **all** reply threading in Slack, including explicit `[[reply_to_*]]` tags. This differs from Telegram, where explicit tags are still honored in `"off"` mode. Slack threads hide messages from the channel while Telegram replies stay visible inline.
535+
</Note>
534536

535537
## Ack reactions
536538

‎docs/channels/whatsapp.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -567,7 +567,9 @@ The effective `direct` map is determined first: if the account defines its own `
567567
1. **Direct-specific system prompt** (`direct["<peerId>"].systemPrompt`): used when the specific peer entry exists in the map **and** its `systemPrompt` key is defined. If `systemPrompt` is an empty string (`""`), the wildcard is suppressed and no system prompt is applied.
568568
2. **Direct wildcard system prompt** (`direct["*"].systemPrompt`): used when the specific peer entry is absent from the map entirely, or when it exists but defines no `systemPrompt` key.
569569

570-
Note: `dms` remains the lightweight per-DM history override bucket (`dms.<id>.historyLimit`); prompt overrides live under `direct`.
570+
<Note>
571+
`dms` remains the lightweight per-DM history override bucket (`dms.<id>.historyLimit`). Prompt overrides live under `direct`.
572+
</Note>
571573

572574
**Difference from Telegram multi-account behavior:** In Telegram, root `groups` is intentionally suppressed for all accounts in a multi-account setup — even accounts that define no `groups` of their own — to prevent a bot from receiving group messages for groups it does not belong to. WhatsApp does not apply this guard: root `groups` and root `direct` are always inherited by accounts that define no account-level override, regardless of how many accounts are configured. In a multi-account WhatsApp setup, if you want per-account group or direct prompts, define the full map under each account explicitly rather than relying on root-level defaults.
573575

0 commit comments

Comments
 (0)