From 59c78c105a772d7015718a5207c022c3d4fe875d Mon Sep 17 00:00:00 2001 From: Vincent Koc Date: Sat, 21 Feb 2026 11:18:29 -0500 Subject: [PATCH] docs: revert automated heading consistency edits (#22743) --- docs/channels/bluebubbles.md | 2 +- docs/channels/discord.md | 4 ++-- docs/channels/feishu.md | 2 +- docs/channels/googlechat.md | 2 +- docs/channels/imessage.md | 4 ++-- docs/channels/line.md | 4 ++-- docs/channels/matrix.md | 4 ++-- docs/channels/mattermost.md | 2 +- docs/channels/msteams.md | 4 ++-- docs/channels/nextcloud-talk.md | 4 ++-- docs/channels/nostr.md | 4 ++-- docs/channels/signal.md | 8 ++++---- docs/channels/slack.md | 4 ++-- docs/channels/telegram.md | 2 +- docs/channels/tlon.md | 2 +- docs/channels/twitch.md | 4 ++-- docs/channels/whatsapp.md | 4 ++-- docs/channels/zalo.md | 6 +++--- docs/channels/zalouser.md | 2 +- docs/tools/thinking.md | 3 +-- 20 files changed, 35 insertions(+), 36 deletions(-) diff --git a/docs/channels/bluebubbles.md b/docs/channels/bluebubbles.md index f9dcff3b61e..8c8267498b7 100644 --- a/docs/channels/bluebubbles.md +++ b/docs/channels/bluebubbles.md @@ -285,7 +285,7 @@ Control whether responses are sent as a single message or streamed in blocks: - Media cap via `channels.bluebubbles.mediaMaxMb` (default: 8 MB). - Outbound text is chunked to `channels.bluebubbles.textChunkLimit` (default: 4000 chars). -## Configuration +## Configuration reference Full configuration: [Configuration](/gateway/configuration) diff --git a/docs/channels/discord.md b/docs/channels/discord.md index de8badec51b..044e8784046 100644 --- a/docs/channels/discord.md +++ b/docs/channels/discord.md @@ -21,7 +21,7 @@ Status: ready for DMs and guild channels via the official Discord gateway. -## Onboarding +## Quick setup You will need to create a new application with a bot, add the bot to your server, and pair it to OpenClaw. We recommend adding your bot to your own private server. If you don't have one yet, [create one first](https://support.discord.com/hc/en-us/articles/204849977-How-do-I-create-a-server) (choose **Create My Own > For me and my friends**). @@ -963,7 +963,7 @@ openclaw logs --follow -## Configuration +## Configuration reference pointers Primary reference: diff --git a/docs/channels/feishu.md b/docs/channels/feishu.md index 8a1853dd24b..e92f84460d3 100644 --- a/docs/channels/feishu.md +++ b/docs/channels/feishu.md @@ -523,7 +523,7 @@ See [Get group/user IDs](#get-groupuser-ids) for lookup tips. --- -## Configuration +## Configuration reference Full configuration: [Gateway configuration](/gateway/configuration) diff --git a/docs/channels/googlechat.md b/docs/channels/googlechat.md index edccc619016..818a8288f5d 100644 --- a/docs/channels/googlechat.md +++ b/docs/channels/googlechat.md @@ -9,7 +9,7 @@ title: "Google Chat" Status: ready for DMs + spaces via Google Chat API webhooks (HTTP only). -## Onboarding +## Quick setup (beginner) 1. Create a Google Cloud project and enable the **Google Chat API**. - Go to: [Google Chat API Credentials](https://console.cloud.google.com/apis/api/chat.googleapis.com/credentials) diff --git a/docs/channels/imessage.md b/docs/channels/imessage.md index 5d6e4bf8955..d7a1b633597 100644 --- a/docs/channels/imessage.md +++ b/docs/channels/imessage.md @@ -28,7 +28,7 @@ Status: legacy external CLI integration. Gateway spawns `imsg rpc` and communica -## Onboarding +## Quick setup @@ -358,7 +358,7 @@ imsg send "test" -## Configuration +## Configuration reference pointers - [Configuration reference - iMessage](/gateway/configuration-reference#imessage) - [Gateway configuration](/gateway/configuration) diff --git a/docs/channels/line.md b/docs/channels/line.md index 32b33ddf81e..d32e683fbeb 100644 --- a/docs/channels/line.md +++ b/docs/channels/line.md @@ -31,7 +31,7 @@ Local checkout (when running from a git repo): openclaw plugins install ./extensions/line ``` -## Onboarding +## Setup 1. Create a LINE Developers account and open the Console: [https://developers.line.biz/console/](https://developers.line.biz/console/) @@ -48,7 +48,7 @@ The gateway responds to LINE’s webhook verification (GET) and inbound events ( If you need a custom path, set `channels.line.webhookPath` or `channels.line.accounts..webhookPath` and update the URL accordingly. -## Configuration +## Configure Minimal config: diff --git a/docs/channels/matrix.md b/docs/channels/matrix.md index ca7a0d9e964..04205d94971 100644 --- a/docs/channels/matrix.md +++ b/docs/channels/matrix.md @@ -36,7 +36,7 @@ OpenClaw will offer the local install path automatically. Details: [Plugins](/tools/plugin) -## Onboarding +## Setup 1. Install the Matrix plugin: - From npm: `openclaw plugins install @openclaw/matrix` @@ -270,7 +270,7 @@ Common failures: For triage flow: [/channels/troubleshooting](/channels/troubleshooting). -## Configuration +## Configuration reference (Matrix) Full configuration: [Configuration](/gateway/configuration) diff --git a/docs/channels/mattermost.md b/docs/channels/mattermost.md index b7668981e7a..fa0d9393e0f 100644 --- a/docs/channels/mattermost.md +++ b/docs/channels/mattermost.md @@ -33,7 +33,7 @@ OpenClaw will offer the local install path automatically. Details: [Plugins](/tools/plugin) -## Onboarding +## Quick setup 1. Install the Mattermost plugin. 2. Create a Mattermost bot account and copy the **bot token**. diff --git a/docs/channels/msteams.md b/docs/channels/msteams.md index 21c35203210..2232582610a 100644 --- a/docs/channels/msteams.md +++ b/docs/channels/msteams.md @@ -38,7 +38,7 @@ OpenClaw will offer the local install path automatically. Details: [Plugins](/tools/plugin) -## Onboarding +## Quick setup (beginner) 1. Install the Microsoft Teams plugin. 2. Create an **Azure Bot** (App ID + client secret + tenant ID). @@ -236,7 +236,7 @@ This is often easier than hand-editing JSON manifests. 2. Find the bot in Teams and send a DM 3. Check gateway logs for incoming activity -## Onboarding (minimal) +## Setup (minimal text-only) 1. **Install the Microsoft Teams plugin** - From npm: `openclaw plugins install @openclaw/msteams` diff --git a/docs/channels/nextcloud-talk.md b/docs/channels/nextcloud-talk.md index 141f811fbd9..d4ab9e2c397 100644 --- a/docs/channels/nextcloud-talk.md +++ b/docs/channels/nextcloud-talk.md @@ -30,7 +30,7 @@ OpenClaw will offer the local install path automatically. Details: [Plugins](/tools/plugin) -## Onboarding +## Quick setup (beginner) 1. Install the Nextcloud Talk plugin. 2. On your Nextcloud server, create a bot: @@ -106,7 +106,7 @@ Minimal config: | Reactions | Supported | | Native commands | Not supported | -## Configuration +## Configuration reference (Nextcloud Talk) Full configuration: [Configuration](/gateway/configuration) diff --git a/docs/channels/nostr.md b/docs/channels/nostr.md index 0d930fff932..3368933d6c4 100644 --- a/docs/channels/nostr.md +++ b/docs/channels/nostr.md @@ -40,7 +40,7 @@ openclaw plugins install --link /extensions/nostr Restart the Gateway after installing or enabling plugins. -## Onboarding +## Quick setup 1. Generate a Nostr keypair (if needed): @@ -69,7 +69,7 @@ export NOSTR_PRIVATE_KEY="nsec1..." 4. Restart the Gateway. -## Configuration +## Configuration reference | Key | Type | Default | Description | | ------------ | -------- | ------------------------------------------- | ----------------------------------- | diff --git a/docs/channels/signal.md b/docs/channels/signal.md index e28238db020..60bb5f7ce92 100644 --- a/docs/channels/signal.md +++ b/docs/channels/signal.md @@ -17,7 +17,7 @@ Status: external CLI integration. Gateway talks to `signal-cli` over HTTP JSON-R - A phone number that can receive one verification SMS (for SMS registration path). - Browser access for Signal captcha (`signalcaptchas.org`) during registration. -## Onboarding +## Quick setup (beginner) 1. Use a **separate Signal number** for the bot (recommended). 2. Install `signal-cli` (Java required if you use the JVM build). @@ -76,7 +76,7 @@ Disable with: - If you run the bot on **your personal Signal account**, it will ignore your own messages (loop protection). - For "I text the bot and it replies," use a **separate bot number**. -## Onboarding (option A): link existing Signal account (QR) +## Setup path A: link existing Signal account (QR) 1. Install `signal-cli` (JVM or native build). 2. Link a bot account: @@ -101,7 +101,7 @@ Example: Multi-account support: use `channels.signal.accounts` with per-account config and optional `name`. See [`gateway/configuration`](/gateway/configuration#telegramaccounts--discordaccounts--slackaccounts--signalaccounts--imessageaccounts) for the shared pattern. -## Onboarding (option B): register dedicated bot number (SMS, Linux) +## Setup path B: register dedicated bot number (SMS, Linux) Use this when you want a dedicated bot number instead of linking an existing Signal app account. @@ -290,7 +290,7 @@ For triage flow: [/channels/troubleshooting](/channels/troubleshooting). - Keep `channels.signal.dmPolicy: "pairing"` unless you explicitly want broader DM access. - SMS verification is only needed for registration or recovery flows, but losing control of the number/account can complicate re-registration. -## Configuration +## Configuration reference (Signal) Full configuration: [Configuration](/gateway/configuration) diff --git a/docs/channels/slack.md b/docs/channels/slack.md index 3e9e4b61b49..9fdd3fb89a2 100644 --- a/docs/channels/slack.md +++ b/docs/channels/slack.md @@ -21,7 +21,7 @@ Status: production-ready for DMs + channels via Slack app integrations. Default -## Onboarding +## Quick setup @@ -487,7 +487,7 @@ channels: - Media and non-text payloads fall back to normal delivery. - If streaming fails mid-reply, OpenClaw falls back to normal delivery for remaining payloads. -## Configuration +## Configuration reference pointers Primary reference: diff --git a/docs/channels/telegram.md b/docs/channels/telegram.md index 01e13ea1aa8..5517ab20efb 100644 --- a/docs/channels/telegram.md +++ b/docs/channels/telegram.md @@ -21,7 +21,7 @@ Status: production-ready for bot DMs + groups via grammY. Long polling is the de -## Onboarding +## Quick setup diff --git a/docs/channels/tlon.md b/docs/channels/tlon.md index 039f322884f..dbd2015c4ef 100644 --- a/docs/channels/tlon.md +++ b/docs/channels/tlon.md @@ -32,7 +32,7 @@ openclaw plugins install ./extensions/tlon Details: [Plugins](/tools/plugin) -## Onboarding +## Setup 1. Install the Tlon plugin. 2. Gather your ship URL and login code. diff --git a/docs/channels/twitch.md b/docs/channels/twitch.md index ff1ff716642..32670f31540 100644 --- a/docs/channels/twitch.md +++ b/docs/channels/twitch.md @@ -27,7 +27,7 @@ openclaw plugins install ./extensions/twitch Details: [Plugins](/tools/plugin) -## Onboarding +## Quick setup (beginner) 1. Create a dedicated Twitch account for the bot (or use an existing account). 2. Generate credentials: [Twitch Token Generator](https://twitchtokengenerator.com/) @@ -67,7 +67,7 @@ Minimal config: - Each account maps to an isolated session key `agent::twitch:`. - `username` is the bot's account (who authenticates), `channel` is which chat room to join. -## Onboarding (detailed, recommended) +## Setup (detailed) ### Generate credentials diff --git a/docs/channels/whatsapp.md b/docs/channels/whatsapp.md index 95d0a2007a3..a6fb427bdc2 100644 --- a/docs/channels/whatsapp.md +++ b/docs/channels/whatsapp.md @@ -21,7 +21,7 @@ Status: production-ready via WhatsApp Web (Baileys). Gateway owns linked session -## Onboarding +## Quick setup @@ -422,7 +422,7 @@ Behavior notes: -## Configuration +## Configuration reference pointers Primary reference: diff --git a/docs/channels/zalo.md b/docs/channels/zalo.md index a3c042c9907..cda126f5649 100644 --- a/docs/channels/zalo.md +++ b/docs/channels/zalo.md @@ -17,7 +17,7 @@ Zalo ships as a plugin and is not bundled with the core install. - Or select **Zalo** during onboarding and confirm the install prompt - Details: [Plugins](/tools/plugin) -## Onboarding +## Quick setup (beginner) 1. Install the Zalo plugin: - From a source checkout: `openclaw plugins install ./extensions/zalo` @@ -53,7 +53,7 @@ It is a good fit for support or notifications where you want deterministic routi - DMs share the agent's main session. - Groups are not yet supported (Zalo docs state "coming soon"). -## Onboarding (quick path) +## Setup (fast path) ### 1) Create a bot token (Zalo Bot Platform) @@ -161,7 +161,7 @@ Multi-account support: use `channels.zalo.accounts` with per-account tokens and - Confirm the gateway HTTP endpoint is reachable on the configured path - Check that getUpdates polling is not running (they're mutually exclusive) -## Configuration +## Configuration reference (Zalo) Full configuration: [Configuration](/gateway/configuration) diff --git a/docs/channels/zalouser.md b/docs/channels/zalouser.md index 24ed6f4baf8..e93e71a6f7e 100644 --- a/docs/channels/zalouser.md +++ b/docs/channels/zalouser.md @@ -27,7 +27,7 @@ The Gateway machine must have the `zca` binary available in `PATH`. - Verify: `zca --version` - If missing, install zca-cli (see `extensions/zalouser/README.md` or the upstream zca-cli docs). -## Onboarding +## Quick setup (beginner) 1. Install the plugin (see above). 2. Login (QR, on the Gateway machine): diff --git a/docs/tools/thinking.md b/docs/tools/thinking.md index 0ea63df40e5..c01ea540f0e 100644 --- a/docs/tools/thinking.md +++ b/docs/tools/thinking.md @@ -49,7 +49,7 @@ title: "Thinking Levels" - When verbose is on, agents that emit structured tool results (Pi, other JSON agents) send each tool call back as its own metadata-only message, prefixed with ` : ` when available (path/command). These tool summaries are sent as soon as each tool starts (separate bubbles), not as streaming deltas. - When verbose is `full`, tool outputs are also forwarded after completion (separate bubble, truncated to a safe length). If you toggle `/verbose on|full|off` while a run is in-flight, subsequent tool bubbles honor the new setting. -## Reasoning visibility (/tools/thinking#reasoning-visibility-reasoning) +## Reasoning visibility (/reasoning) - Levels: `on|off|stream`. - Directive-only message toggles whether thinking blocks are shown in replies. @@ -61,7 +61,6 @@ title: "Thinking Levels" ## Related - Elevated mode docs live in [Elevated mode](/tools/elevated). -- Reasoning visibility behavior is documented in [Reasoning visibility](/tools/thinking#reasoning-visibility-reasoning). ## Heartbeats