sz-chrome-remote-cdp.git/castle-search/src/google-links.ts, branch master 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-11-06T03:33:30+00:00 castle-search: resolve Google links lazily, in Chrome, not eagerly over plain HTTP 2026-11-06T03:33:30+00:00 Igor Soarez igor@soarez.org 2026-11-06T03:33:30+00:00 urn:sha1:561f0ee076c684a79fd5671af1bad0894f33e4de The Node-side resolver sent one curl-like request per result with no cookies, JS or browser; Google answers that with its 'Verifying your request' countdown after a handful, and the testing itself triggered it. A click or direct navigation in Chrome redirects at once (measured). Search now leaves Google links wrapped and prints the breadcrumb Google shows for each. castle_cdp_resolve follows one wrapped link in a Chrome tab when the agent picks it, accepts only google.com/goto?url=<token>, and reports the verification page instead of waiting it out.