pi-browser-harness, patched to drive a Chrome on another host over CDP, with castle_cdp_search web search https://git.soarez.net/sz/sz-chrome-remote-cdp.git/atom?h=master 2026-08-02T13:42:46+00:00 2026-08-02T13:42:46+00:00 amankumarsingh77 amankumarsingh7702@gmail.com 2026-07-28T16:18:35+00:00 urn:sha1:6d300099a86cfdb92b7869dc2b4f33094554b24c Both were documented and inert. --browser-debug-clicks was registered as a flag and never read; the only real switch was the undocumented BH_DEBUG_CLICKS env var. The flag now feeds util/debug.ts, which the click tool consults, and the env var keeps working as an equivalent. BU_CDP_WS was read in the client and handed to transport.connect(), but the daemon transport discards that argument and always dials the daemon socket — and the daemon's own discovery never looked at the variable, so setting it did nothing. The override now lives in discoverEndpoint, which is what both processes go through, and the client's redundant read is gone. The variable must be set before the daemon spawns. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>