docs(browser): document local startup timeout bounds (#71672) · openclaw/openclaw@8170df9
Quratulain-b
·
2026-04-26
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -280,7 +280,8 @@ See [Plugins](/tools/plugin).
|
280 | 280 | - Local managed profiles use `browser.localLaunchTimeoutMs` for Chrome CDP HTTP |
281 | 281 | discovery after process start and `browser.localCdpReadyTimeoutMs` for |
282 | 282 | post-launch CDP websocket readiness. Raise them on slower hosts where Chrome |
283 | | - starts successfully but readiness checks race startup. |
| 283 | + starts successfully but readiness checks race startup. Both values must be |
| 284 | + positive integers up to `120000` ms; invalid config values are rejected. |
284 | 285 | - Auto-detect order: default browser if Chromium-based → Chrome → Brave → Edge → Chromium → Chrome Canary. |
285 | 286 | - `browser.executablePath` accepts `~` for your OS home directory. |
286 | 287 | - Control service: loopback only (port derived from `gateway.port`, default `18791`). |
|
| Original file line number | Diff line number | Diff line change |
|---|
@@ -140,8 +140,8 @@ curl -s http://127.0.0.1:18791/tabs
|
140 | 140 | On Raspberry Pi, older VPS hosts, or slow storage, raise |
141 | 141 | `browser.localLaunchTimeoutMs` when Chrome needs more time to expose its CDP HTTP |
142 | 142 | endpoint. Raise `browser.localCdpReadyTimeoutMs` when launch succeeds but |
143 | | -`openclaw browser start` still reports `not reachable after start`. Values are |
144 | | -capped at 120000 ms. |
| 143 | +`openclaw browser start` still reports `not reachable after start`. Values must |
| 144 | +be positive integers up to `120000` ms; invalid config values are rejected. |
145 | 145 | |
146 | 146 | ### Problem: "No Chrome tabs found for profile=\"user\"" |
147 | 147 | |
|
| Original file line number | Diff line number | Diff line change |
|---|
@@ -200,7 +200,8 @@ Browser settings live in `~/.openclaw/openclaw.json`.
|
200 | 200 | process to expose its CDP HTTP endpoint. `localCdpReadyTimeoutMs` is the |
201 | 201 | follow-up budget for CDP websocket readiness after the process is discovered. |
202 | 202 | Raise these on Raspberry Pi, low-end VPS, or older hardware where Chromium |
203 | | - starts slowly. Values are capped at 120000 ms. |
| 203 | + starts slowly. Values must be positive integers up to `120000` ms; invalid |
| 204 | + config values are rejected. |
204 | 205 | - `actionTimeoutMs` is the default budget for browser `act` requests when the caller does not pass `timeoutMs`. The client transport adds a small slack window so long waits can finish instead of timing out at the HTTP boundary. |
205 | 206 | - `tabCleanup` is best-effort cleanup for tabs opened by primary-agent browser sessions. Subagent, cron, and ACP lifecycle cleanup still closes their explicit tracked tabs at session end; primary sessions keep active tabs reusable, then close idle or excess tracked tabs in the background. |
206 | 207 | |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
