From 08c0c3a8b4fe755f7fe65ea8d258d77971503882 Mon Sep 17 00:00:00 2001 From: Igor Soarez Date: Thu, 15 Oct 2026 22:25:41 +0100 Subject: fix(cdp): give the castle default 1.5s, not 5s, inside upstream's connect budget --- FORK.md | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'FORK.md') diff --git a/FORK.md b/FORK.md index d106983..8464128 100644 --- a/FORK.md +++ b/FORK.md @@ -99,6 +99,10 @@ The asymmetry is deliberate. An explicit endpoint is an instruction, so failing to reach it must not quietly automate a different browser — that would drive your own signed-in Chrome instead of the shared one. The default is only a preference, so a laptop away from the wire network still gets the local browser. +The default is given 1.5s to answer, explicit targets 5s: upstream 0.11 starts +the bridge's 10s connect timer before discovery, and off wg8 the castle address +times out rather than being refused, so a 5s probe left a local Chrome only +about 5s for its "Allow remote debugging?" prompt. `/browser-status` names the resolved target and whether it is reachable. Note the connection is **lazy**: nothing dials the browser until the first `browser_*` -- cgit v1.2.3