chore(sync): mirror docs from openclaw/openclaw@1de74bdc59

.openclaw-sync/source.json

@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "c35ed548bf0c6bad052d822d7607889e100efd08",
-  "syncedAt": "2026-05-02T08:13:42.896Z"
+  "sha": "1de74bdc5906fed8c692f3621b19a3b625704a9f",
+  "syncedAt": "2026-05-02T08:22:39.935Z"
 }

docs/gateway/cli-backends.md

@@ -210,6 +210,12 @@ binary is not already on `PATH`.
   ids are verified against an existing readable project transcript before
   resume, so phantom bindings are cleared with `reason=transcript-missing`
   instead of silently starting a fresh Claude CLI session under `--resume`.
+- Claude live sessions keep bounded JSONL output guards. Defaults allow up to
+  8 MiB and 20,000 raw JSONL lines per turn. Tool-heavy Claude turns can raise
+  them per backend with
+  `agents.defaults.cliBackends.claude-cli.reliability.outputLimits.maxTurnRawChars`
+  and `maxTurnLines`; OpenClaw clamps those settings to 64 MiB and 100,000
+  lines.
 - Stored CLI sessions are provider-owned continuity. The implicit daily session
   reset does not cut them; `/reset` and explicit `session.reset` policies still
   do.