From d129be8634551db3d2724f7c026fab65f38ea224 Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Fri, 24 Apr 2026 05:26:39 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@aca92b29065fef29b187e1303f0c5beec42f9c0f --- .openclaw-sync/source.json | 4 ++-- docs/concepts/dreaming.md | 12 ------------ docs/plugins/google-meet.md | 8 +++++++- 3 files changed, 9 insertions(+), 15 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 97bee7c91..6fa5d3507 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "0ad058a9cbc67842d64eff6f4c1a89bf1f44779c", - "syncedAt": "2026-04-24T05:19:17.225Z" + "sha": "aca92b29065fef29b187e1303f0c5beec42f9c0f", + "syncedAt": "2026-04-24T05:25:05.087Z" } diff --git a/docs/concepts/dreaming.md b/docs/concepts/dreaming.md index e2687c465..6f107b5c9 100644 --- a/docs/concepts/dreaming.md +++ b/docs/concepts/dreaming.md @@ -227,20 +227,8 @@ When enabled, the Gateway **Dreams** tab shows: - a distinct grounded Scene lane for staged historical replay entries - an expandable Dream Diary reader backed by `doctor.memory.dreamDiary` -## Troubleshooting - -### Dreaming never runs (status shows blocked) - -The managed dreaming cron rides the default agent's heartbeat. If heartbeat is not firing for that agent, the cron enqueues a system event that nobody consumes and dreaming silently does not run. Both `openclaw memory status` and `/dreaming status` will report `blocked` in that case and name the agent whose heartbeat is the blocker. - -Two common causes: - -- Another agent declares an explicit `heartbeat:` block. When any entry in `agents.list` has its own `heartbeat` block, only those agents heartbeat — the defaults stop applying to everyone else, so the default agent can go silent. Move the heartbeat settings to `agents.defaults.heartbeat`, or add an explicit `heartbeat` block on the default agent. See [Scope and precedence](/gateway/heartbeat#scope-and-precedence). -- `heartbeat.every` is `0`, empty, or unparsable. The cron has no interval to schedule against, so the heartbeat is effectively disabled. Set `every` to a positive duration such as `30m`. See [Defaults](/gateway/heartbeat#defaults). - ## Related -- [Heartbeat](/gateway/heartbeat) - [Memory](/concepts/memory) - [Memory Search](/concepts/memory-search) - [memory CLI](/cli/memory) diff --git a/docs/plugins/google-meet.md b/docs/plugins/google-meet.md index 8ea99bff0..2ddd662bf 100644 --- a/docs/plugins/google-meet.md +++ b/docs/plugins/google-meet.md @@ -169,6 +169,11 @@ Route Meet through that node on the Gateway host: ```json5 { + gateway: { + nodes: { + allowCommands: ["googlemeet.chrome"], + }, + }, plugins: { entries: { "google-meet": { @@ -201,7 +206,8 @@ Common failure checks: - `No connected Google Meet-capable node`: start `openclaw node run` in the VM, approve pairing, and make sure `openclaw plugins enable google-meet` was run - in the VM. + in the VM. Also confirm the Gateway host allows the node command with + `gateway.nodes.allowCommands: ["googlemeet.chrome"]`. - `BlackHole 2ch audio device not found on the node`: install `blackhole-2ch` in the VM and reboot the VM. - Chrome opens but cannot join: sign in to Chrome inside the VM and confirm that