Search castle's Chrome tabs and history over CDP https://git.soarez.net/sz/pi-castle-cdp-search.git/atom/docs/2026-08-04-ai-answers.md?h=master 2026-08-04T14:08:47Z 2026-08-04T14:08:47Z Igor Soarez igor@soarez.org 2026-08-04T14:08:47Z urn:sha1:4ad98a78bebf787bde419ab245f970a4885b1b15 Google, Bing and Brave all put a generated answer above their results now, and none of it is being read. Investigated against castle's Chrome; nothing in src/ changed, because the cost turned out to be worth deciding on rather than absorbing. Two things make it expensive. Google's AI Overview exists only on the classic layout — udm=14 is the "Web" tab, and having no overview is part of what that tab is — so enabling it means giving back the clean page the extractor was built around. And all three stream in after the results are already parseable: Google settles ~2.3s in, Brave was still growing at 5s, against an extractor that returns at ~0.5s. The wait is often wasted, since the blocks are query-dependent — no Google overview for "how does postgres MVCC vacuum work" after 15s, no Bing answer for "who founded anthropic". Selectors, the traps behind them (#m-x-content briefly holds ~29k characters of unrelated page; Google's "Show more" hides only the disclaimer), the measured timings, three possible designs and their tradeoffs are all in the doc, so this does not have to be re-measured if the answer turns out to be yes.