diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index aa8ed383b..73a0727b8 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "98d87b06e0a2ad8f8d447d9cf1e917df78ec5271", - "syncedAt": "2026-05-01T02:40:48.268Z" + "sha": "6603a174bcc6d68213ee4e0a05c833f791dd87f0", + "syncedAt": "2026-05-01T02:49:37.415Z" } diff --git a/docs/.generated/config-baseline.sha256 b/docs/.generated/config-baseline.sha256 index e96d3eb8f..3f6a354ab 100644 --- a/docs/.generated/config-baseline.sha256 +++ b/docs/.generated/config-baseline.sha256 @@ -1,4 +1,4 @@ -f2f5dc47ab9572fa5f80eb01b5a176edb04ca91c7a25bea3b9ea8e19dd21904b config-baseline.json -d81f9cadab9762a4b542795ed1f01f27e374f9811cf176f08cbbb7a20b044c15 config-baseline.core.json +a69e6b650513c2a697ee51087928bf78f63ba998c7c60f8cca61dd65a0184fd0 config-baseline.json +0a259216178a582c567d1fa48c5236bff4bbd27c3e6af838ffcd042459ffce3c config-baseline.core.json 92712871defa92eeda8161b516db85574681f2b70678b940508a808b987aeae2 config-baseline.channel.json 6005cf9f6e8c9f25ef97207b5eee29ae0e506cf910cdeca77fc9894ad1755b1f config-baseline.plugin.json diff --git a/docs/automation/tasks.md b/docs/automation/tasks.md index c7076ae94..c90865976 100644 --- a/docs/automation/tasks.md +++ b/docs/automation/tasks.md @@ -96,13 +96,13 @@ Not every agent run creates a task. Heartbeat turns and normal interactive chat | Subagent orchestration | `subagent` | Spawning a subagent via `sessions_spawn` | `done_only` | | Cron jobs (all types) | `cron` | Every cron execution (main-session and isolated) | `silent` | | CLI operations | `cli` | `openclaw agent` commands that run through the gateway | `silent` | -| Agent media jobs | `cli` | Session-backed `video_generate` runs | `silent` | +| Agent media jobs | `cli` | Session-backed `music_generate`/`video_generate` runs | `silent` | Main-session cron tasks use `silent` notify policy by default — they create records for tracking but do not generate notifications. Isolated cron tasks also default to `silent` but are more visible because they run in their own session. - Session-backed `video_generate` runs also use `silent` notify policy. They still create task records, but completion is handed back to the original agent session as an internal wake so the agent can write the follow-up message and attach the finished video itself. If you opt into `tools.media.asyncCompletion.directSend`, async `music_generate` and `video_generate` completions try direct channel delivery first before falling back to the requester-session wake path. + Session-backed `music_generate` and `video_generate` runs also use `silent` notify policy. They still create task records, but completion is handed back to the original agent session as an internal wake so the agent can write the follow-up message and attach the finished media itself. If you opt into `tools.media.asyncCompletion.directSend`, async `video_generate` completions can try direct channel delivery first; async `music_generate` completions stay on the requester-session wake path. diff --git a/docs/gateway/config-tools.md b/docs/gateway/config-tools.md index ebf7969d2..82f2a4157 100644 --- a/docs/gateway/config-tools.md +++ b/docs/gateway/config-tools.md @@ -201,7 +201,7 @@ Configures inbound media understanding (image/audio/video): media: { concurrency: 2, asyncCompletion: { - directSend: false, // opt-in: send finished async music/video directly to the channel + directSend: false, // opt-in: send finished async video directly to the channel }, audio: { enabled: true, @@ -254,7 +254,7 @@ Configures inbound media understanding (image/audio/video): **Async completion fields:** - - `asyncCompletion.directSend`: when `true`, completed async `music_generate` and `video_generate` tasks try direct channel delivery first. Default: `false` (legacy requester-session wake/model-delivery path). + - `asyncCompletion.directSend`: when `true`, completed async media tasks that support direct completion delivery try direct channel delivery first. Default: `false` (requester-session wake/model-delivery path). Today this applies to async `video_generate`; async `music_generate` completions stay requester-session mediated even when this is enabled.