- Local managed profiles use `browser.localLaunchTimeoutMs` for Chrome CDP HTTP

discovery after process start and `browser.localCdpReadyTimeoutMs` for

post-launch CDP websocket readiness. Raise them on slower hosts where Chrome

starts successfully but readiness checks race startup.

starts successfully but readiness checks race startup. Both values must be

positive integers up to `120000` ms; invalid config values are rejected.

- Auto-detect order: default browser if Chromium-based → Chrome → Brave → Edge → Chromium → Chrome Canary.

- `browser.executablePath` accepts `~` for your OS home directory.

- Control service: loopback only (port derived from `gateway.port`, default `18791`).

On Raspberry Pi, older VPS hosts, or slow storage, raise

`browser.localLaunchTimeoutMs` when Chrome needs more time to expose its CDP HTTP

endpoint. Raise `browser.localCdpReadyTimeoutMs` when launch succeeds but

`openclaw browser start` still reports `not reachable after start`. Values are

capped at 120000 ms.

`openclaw browser start` still reports `not reachable after start`. Values must

be positive integers up to `120000` ms; invalid config values are rejected.

### Problem: "No Chrome tabs found for profile=\"user\""

process to expose its CDP HTTP endpoint. `localCdpReadyTimeoutMs` is the

follow-up budget for CDP websocket readiness after the process is discovered.

Raise these on Raspberry Pi, low-end VPS, or older hardware where Chromium

starts slowly. Values are capped at 120000 ms.

starts slowly. Values must be positive integers up to `120000` ms; invalid

config values are rejected.

- `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.

- `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.