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

.openclaw-sync/source.json

@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "9d27d09d4762b8588f37b890db8d536a0e7aca0e",
-  "syncedAt": "2026-04-22T17:33:15.731Z"
+  "sha": "dad4b3e7fb07648b175cec56807d00471dde5c0c",
+  "syncedAt": "2026-04-22T17:39:21.825Z"
 }

docs/gateway/cli-backends.md

@@ -181,10 +181,10 @@ child process environment for the run.
   - `always`: always send a session id (new UUID if none stored).
   - `existing`: only send a session id if one was stored before.
   - `none`: never send a session id.
-- The bundled `claude-cli` backend uses `liveSession: "claude-stdio"` so
-  follow-up turns reuse the live Claude process while it is active. If the
-  Gateway restarts or the idle process exits, OpenClaw resumes from the stored
-  Claude session id.
+- `claude-cli` defaults to `liveSession: "claude-stdio"`, `output: "jsonl"`,
+  and `input: "stdin"` so follow-up turns reuse the live Claude process while
+  it is active. If the Gateway restarts or the idle process exits, OpenClaw
+  resumes from the stored Claude session id.
 - Stored CLI sessions are provider-owned continuity. The implicit daily session
   reset does not cut them; `/reset` and explicit `session.reset` policies still
   do.