From 3a0bfc3af446a947f8392aaa3e3b2605ea7ad2da Mon Sep 17 00:00:00 2001 From: Igor Soarez Date: Sun, 30 Aug 2026 16:17:49 +0100 Subject: docs: castle restarts Chrome on failure, not hourly --- FORK.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/FORK.md b/FORK.md index 853b812..4e78478 100644 --- a/FORK.md +++ b/FORK.md @@ -31,8 +31,9 @@ Without the patch the only option is relaying the remote browser onto localhost client both honour it. It names an **HTTP** endpoint, not a WebSocket URL, because it is re-resolved on every discovery call — the browser UUID is re-read after the remote browser restarts. Chrome re-mints that UUID on every launch, so -a pinned WebSocket URL breaks as soon as the remote browser is recycled (castle -recycles Chrome hourly; see `cloud-setup/macos/chrome-cdp.sh`). +a pinned WebSocket URL breaks as soon as the remote browser restarts (castle's +watchdog restarts Chrome whenever CDP stops answering, plus once a day; see +`cloud-setup/macos/chrome-cdp.sh`). ## Install -- cgit v1.2.3