From be51bb704b0058100fe825c2c78ab9a803620144 Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Tue, 28 Apr 2026 19:50:16 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@0dcab4e34760cac5d9cd02649d4b3a5c2f7e5712 --- .openclaw-sync/source.json | 4 ++-- docs/start/bootstrapping.md | 6 ++++++ docs/tools/acp-agents.md | 1 + 3 files changed, 9 insertions(+), 2 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 4978637d8..a8b36c25b 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "3ae69498e2f168e0e4f4de90608d13d9548a570f", - "syncedAt": "2026-04-28T19:47:49.528Z" + "sha": "0dcab4e34760cac5d9cd02649d4b3a5c2f7e5712", + "syncedAt": "2026-04-28T19:48:43.986Z" } diff --git a/docs/start/bootstrapping.md b/docs/start/bootstrapping.md index d754e55ef..9eb7e959e 100644 --- a/docs/start/bootstrapping.md +++ b/docs/start/bootstrapping.md @@ -22,6 +22,12 @@ On the first agent run, OpenClaw bootstraps the workspace (default - Writes identity + preferences to `IDENTITY.md`, `USER.md`, `SOUL.md`. - Removes `BOOTSTRAP.md` when finished so it only runs once. +For embedded/local model runs, OpenClaw keeps `BOOTSTRAP.md` out of the +privileged system context. On the primary interactive first run, it still passes +the file contents in the user prompt so models that do not reliably call the +`read` tool can complete the ritual. If the current run cannot safely access the +workspace, the agent gets a limited bootstrap note instead of a generic greeting. + ## Skipping bootstrapping To skip this for a pre-seeded workspace, run `openclaw onboard --skip-bootstrap`. diff --git a/docs/tools/acp-agents.md b/docs/tools/acp-agents.md index 7f92c038d..74952fd79 100644 --- a/docs/tools/acp-agents.md +++ b/docs/tools/acp-agents.md @@ -142,6 +142,7 @@ Quick `/acp` flow from chat: - Spawn creates or resumes an ACP runtime session, records ACP metadata in the OpenClaw session store, and may create a background task when the run is parent-owned. + - Parent-owned ACP sessions are treated as background work even when the runtime session is persistent; completion and cross-surface delivery go through the parent task notifier rather than acting like a normal user-facing chat session. - Bound follow-up messages go directly to the ACP session until the binding is closed, unfocused, reset, or expired. - Gateway commands stay local. `/acp ...`, `/status`, and `/unfocus` are never sent as normal prompt text to a bound ACP harness. - `cancel` aborts the active turn when the backend supports cancellation; it does not delete the binding or session metadata.