diff options
| author | Igor Soarez <igor@soarez.me> | 2026-08-30 16:17:49 +0100 |
|---|---|---|
| committer | Igor Soarez <igor@soarez.org> | 2026-10-14 12:19:26 +0100 |
| commit | 3a0bfc3af446a947f8392aaa3e3b2605ea7ad2da (patch) | |
| tree | 5a4eac6a98c1ad672732d40b566e9f7bd5e0ac3a | |
| parent | cfa0b6f854e7f15717db385df0e43f974a4b1e67 (diff) | |
docs: castle restarts Chrome on failure, not hourly
| -rw-r--r-- | FORK.md | 5 |
1 files changed, 3 insertions, 2 deletions
@@ -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 |