chore(sync): mirror docs from openclaw/openclaw@b6be422306

This commit is contained in:
openclaw-docs-sync[bot] 2026-04-27 20:39:49 +00:00
parent acb19cfc0a
commit a7a1d8bec3
2 changed files with 3 additions and 3 deletions

View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "599b1b84620bc9c43e37a385d6f5468289e5156e",
"syncedAt": "2026-04-27T20:38:02.043Z"
"sha": "b6be42230672ea2983cbec204217bd2cd7b255a0",
"syncedAt": "2026-04-27T20:38:17.681Z"
}

View File

@ -150,7 +150,7 @@ If an isolated run hits a live model-switch handoff, cron retries with the switc
| `webhook` | POST finished event payload to a URL |
| `none` | No runner fallback delivery |
Use `--announce --channel telegram --to "-1001234567890"` for channel delivery. For Telegram forum topics, use `-1001234567890:topic:123`. Slack/Discord/Mattermost targets should use explicit prefixes (`channel:<id>`, `user:<id>`). Matrix room IDs are case-sensitive; use the exact room ID or `room:!room:server` form from Matrix.
Use `--announce --channel telegram --to "-1001234567890"` for channel delivery. For Telegram forum topics, use `-1001234567890:topic:123`; direct RPC/config callers may also pass `delivery.threadId` as a string or number. Slack/Discord/Mattermost targets should use explicit prefixes (`channel:<id>`, `user:<id>`). Matrix room IDs are case-sensitive; use the exact room ID or `room:!room:server` form from Matrix.
For isolated jobs, chat delivery is shared. If a chat route is available, the agent can use the `message` tool even when the job uses `--no-deliver`. If the agent sends to the configured/current target, OpenClaw skips the fallback announce. Otherwise `announce`, `webhook`, and `none` only control what the runner does with the final reply after the agent turn.