From 6038725501ec943a7b8a89308f3528ae239afa76 Mon Sep 17 00:00:00 2001 From: Vincent Koc Date: Sun, 26 Apr 2026 22:14:57 -0700 Subject: [PATCH] docs: batch convert remaining prose callouts to Mintlify components - platforms/android: blockquote Note for Android app status, Note for canvas host port - platforms/macos: Tip component for app vs CLI discovery comparison - plugins/zalouser, channels/zalouser: blockquote Warning components for unofficial automation risk - channels/pairing: convert two Important paragraphs to Note components for DM-vs-group scope and silent-upgrade behavior --- docs/channels/pairing.md | 13 ++++++------- docs/channels/zalouser.md | 4 +++- docs/platforms/android.md | 8 ++++++-- docs/platforms/macos.md | 7 +++---- docs/plugins/zalouser.md | 4 +++- 5 files changed, 21 insertions(+), 15 deletions(-) diff --git a/docs/channels/pairing.md b/docs/channels/pairing.md index 6ad636f7799..bf484071ee0 100644 --- a/docs/channels/pairing.md +++ b/docs/channels/pairing.md @@ -52,8 +52,9 @@ Account scoping behavior: Treat these as sensitive (they gate access to your assistant). -Important: this store is for DM access. Group authorization is separate. -Approving a DM pairing code does not automatically allow that sender to run group commands or control the bot in groups. For group access, configure the channel's explicit group allowlists (for example `groupAllowFrom`, `groups`, or per-group/per-topic overrides depending on the channel). + +This store is for DM access. Group authorization is separate. Approving a DM pairing code does not automatically allow that sender to run group commands or control the bot in groups. For group access, configure the channel's explicit group allowlists (for example `groupAllowFrom`, `groups`, or per-group or per-topic overrides depending on the channel). + ## 2) Node device pairing (iOS/Android/macOS/headless nodes) @@ -100,11 +101,9 @@ If the same device retries with different auth details (for example different role/scopes/public key), the previous pending request is superseded and a new `requestId` is created. -Important: an already paired device does not get broader access silently. If it -reconnects asking for more scopes or a broader role, OpenClaw keeps the -existing approval as-is and creates a fresh pending upgrade request. Use -`openclaw devices list` to compare the currently approved access with the newly -requested access before you approve. + +An already paired device does not get broader access silently. If it reconnects asking for more scopes or a broader role, OpenClaw keeps the existing approval as-is and creates a fresh pending upgrade request. Use `openclaw devices list` to compare the currently approved access with the newly requested access before you approve. + ### Optional trusted-CIDR node auto-approve diff --git a/docs/channels/zalouser.md b/docs/channels/zalouser.md index a8932715020..84236ff8675 100644 --- a/docs/channels/zalouser.md +++ b/docs/channels/zalouser.md @@ -8,7 +8,9 @@ title: "Zalo personal" Status: experimental. This integration automates a **personal Zalo account** via native `zca-js` inside OpenClaw. -> **Warning:** This is an unofficial integration and may result in account suspension/ban. Use at your own risk. + +This is an unofficial integration and may result in account suspension or ban. Use at your own risk. + ## Bundled plugin diff --git a/docs/platforms/android.md b/docs/platforms/android.md index c42b2f28a57..65a10c87616 100644 --- a/docs/platforms/android.md +++ b/docs/platforms/android.md @@ -7,7 +7,9 @@ read_when: title: "Android app" --- -> **Note:** The Android app has not been publicly released yet. The source code is available in the [OpenClaw repository](https://github.com/openclaw/openclaw) under `apps/android`. You can build it yourself using Java 17 and the Android SDK (`./gradlew :app:assemblePlayDebug`). See [apps/android/README.md](https://github.com/openclaw/openclaw/blob/main/apps/android/README.md) for build instructions. + +The Android app has not been publicly released yet. The source code is available in the [OpenClaw repository](https://github.com/openclaw/openclaw) under `apps/android`. You can build it yourself using Java 17 and the Android SDK (`./gradlew :app:assemblePlayDebug`). See [apps/android/README.md](https://github.com/openclaw/openclaw/blob/main/apps/android/README.md) for build instructions. + ## Support snapshot @@ -170,7 +172,9 @@ The Android Chat tab supports session selection (default `main`, plus other exis If you want the node to show real HTML/CSS/JS that the agent can edit on disk, point the node at the Gateway canvas host. -Note: nodes load canvas from the Gateway HTTP server (same port as `gateway.port`, default `18789`). + +Nodes load canvas from the Gateway HTTP server (same port as `gateway.port`, default `18789`). + 1. Create `~/.openclaw/workspace/canvas/index.html` on the gateway host. diff --git a/docs/platforms/macos.md b/docs/platforms/macos.md index 80473a6ddd5..93e4a2359d3 100644 --- a/docs/platforms/macos.md +++ b/docs/platforms/macos.md @@ -193,10 +193,9 @@ Discovery options: - `--timeout `: overall discovery window (default: `2000`) - `--json`: structured output for diffing -Tip: compare against `openclaw gateway discover --json` to see whether the -macOS app’s discovery pipeline (`local.` plus the configured wide-area domain, with -wide-area and Tailscale Serve fallbacks) differs from -the Node CLI’s `dns-sd` based discovery. + +Compare against `openclaw gateway discover --json` to see whether the macOS app's discovery pipeline (`local.` plus the configured wide-area domain, with wide-area and Tailscale Serve fallbacks) differs from the Node CLI's `dns-sd` based discovery. + ## Remote connection plumbing (SSH tunnels) diff --git a/docs/plugins/zalouser.md b/docs/plugins/zalouser.md index 77789a7eea5..9701db9ff88 100644 --- a/docs/plugins/zalouser.md +++ b/docs/plugins/zalouser.md @@ -10,7 +10,9 @@ title: "Zalo personal plugin" Zalo Personal support for OpenClaw via a plugin, using native `zca-js` to automate a normal Zalo user account. -> **Warning:** Unofficial automation may lead to account suspension/ban. Use at your own risk. + +Unofficial automation may lead to account suspension or ban. Use at your own risk. + ## Naming