browser-control tested by Argusic Runner

Attempt 1 of 3 · Runs · Argusic Score 100.0 of 100

all runs of browser-controlagentbrowser-automationllmrust

Session recording

Loading recording...

Download the original recording · fingerprint 954b8eca835ac066...

What the test found

The browser-control CLI builds and passes all 10 unit tests; the binary connects to Chromium 127 over CDP and successfully executes open, snapshot, eval, cdp, text, and inspect commands against real web pages.

All 4 errors were fixed. The browser-control binary (8.2M release, 76M debug) works with Chromium 127. The only caveat is that browser-control launch doesn't pass --no-sandbox, so in containers without kernel sandbox support Chrome must be started separately with that flag. The BROWSER_CONTROL_CDP_WS env var is the cleanest integration path.

Argusic installed browser-control in 9 minutes and launched it; verification reached Verified running for real. 4 of 4 recorded errors were worked through (see the timeline below).

Runsall runs of browser-control

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.

Error and fix timeline

No errors were recorded for this run.

Discussion