update global AGENTS with test updates, update browser-harness and artifact presenter for html view

This commit is contained in:
jb
2026-08-27 00:55:26 -04:00
parent cf9770b71d
commit 4bbd6a6d06
3 changed files with 49 additions and 7 deletions
+29
View File
@@ -46,6 +46,35 @@ chrome://inspect/#remote-debugging
Ask the user to tick "Allow remote debugging for this browser instance" and click Allow if Chrome shows a permission popup. Then retry the same `browser-harness` command.
## Local HTML fallback (Vivaldi)
Use this fallback only to present a local HTML artifact when normal Chrome attachment is unavailable. An existing Vivaldi can absorb `vivaldi --remote-debugging-port=9222`, causing its launcher to exit without exposing CDP. Launch a separate Vivaldi process with an isolated profile. For a persistent launch, use the coding harness's tracked background-task facility when available rather than shell `&`:
```bash
vivaldi --remote-debugging-port=9222 --user-data-dir=/tmp/pi-vivaldi-cdp --no-first-run file:///absolute/path/to/artifact.html
```
Reload the harness daemon before connecting so it drops any stale Chrome connection:
```bash
browser-harness --reload
BU_CDP_URL=http://127.0.0.1:9222 browser-harness <<'PY'
print(page_info())
PY
```
If `page_info()` initially times out on Vivaldi's blank attached target, inspect the targets, open the artifact in a new tab, and verify again:
```bash
BU_CDP_URL=http://127.0.0.1:9222 browser-harness <<'PY'
print(cdp('Target.getTargets'))
new_tab('file:///absolute/path/to/artifact.html')
print(page_info())
PY
```
Completion criterion: `page_info()` reports the artifact's file URL and page title.
## Remote Browsers
Use Browser Use cloud for headless servers, parallel sub-agents, or isolated work.