fix: split image setup and request timeout semantics

clawsweeper[bot] · clawsweeper[bot] · commit 001dee3fb088 · 2026-06-13T13:21:33.000Z
diff --git a/docs/plugins/codex-harness-reference.md b/docs/plugins/codex-harness-reference.md
@@ -318,6 +318,8 @@ available timeout in this order:
   earlier preparation work.
 - The 90 second dynamic-tool default.
 
+This watchdog is the outer dynamic `item/tool/call` budget. Provider-specific
+request timeouts run inside that call and keep their own timeout semantics.
 Dynamic tool budgets are capped at 600000 ms. On timeout, OpenClaw aborts the
 tool signal where supported and returns a failed dynamic-tool response to Codex
 so the turn can continue instead of leaving the session in `processing`.
diff --git a/docs/plugins/codex-harness.md b/docs/plugins/codex-harness.md
@@ -563,6 +563,8 @@ reduced by earlier preparation work. Dynamic tool budgets are
 capped at 600000 ms. On timeout, OpenClaw aborts the tool signal
 where supported and returns a failed dynamic-tool response to Codex so the turn
 can continue instead of leaving the session in `processing`.
+This watchdog is the outer dynamic `item/tool/call` budget; provider-specific
+request timeouts run inside that call and keep their own timeout semantics.
 
 After Codex accepts a turn, and after OpenClaw responds to a turn-scoped
 app-server request, the harness expects Codex to make current-turn progress and
