feat: human-like typing for browser Google and YouTube search
Some checks failed
Release / semantic-release (push) Successful in 26s
tests / Unit tests (Linux, Python 3.11) (push) Failing after 5m16s
Release / build-linux (push) Failing after 7m11s
Release / build-windows (push) Has been cancelled
Release / build-macos (arm64, macos-latest) (push) Has been cancelled
Release / build-macos (x64, macos-15-intel) (push) Has been cancelled
Release / release-main (push) Has been cancelled
Release / release-develop (push) Has been cancelled

Make the browser search helper search the way a person does: load the
site home page, type the query into the search box one key at a time, and
press Enter — for both Google `search` and `youtube` — instead of jumping
straight to a results URL. Supports the goal of a human-like assistant.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
javis-bot
2026-06-22 21:09:15 +09:00
parent 597207dd33
commit c56ce1eb30
2 changed files with 21 additions and 3 deletions

View File

@@ -22,7 +22,10 @@ path (evals, text entry) and falls back to the master flag:
- **on-screen Chrome**: `browser_search()` drives Chrome (Node CDP helper
`bot/scripts/stream-test/browse-search.mjs`) to Google-search the query, so
the action is visible on the Go-Live broadcast. When no broadcast Chrome is
the action is visible on the Go-Live broadcast. The helper searches the
human way — it loads the site home page, types the query into the search box
one key at a time, and presses Enter (both Google `search` and `youtube`),
rather than jumping to a results URL. When no broadcast Chrome is
reachable on CDP (e.g. a plain text turn with no active broadcast), the helper
falls back, for `search` only, to launching its own Chrome so browser-based
Google search still works with no API cost. Fallback order: