steel-browser tested by Argusic Runner

What the test found

With a user-local Node 22 and Chrome for Testing plus DISABLE_CHROME_SANDBOX=true, the dev-mode API runs on port 3000, /v1/health returns 200 with live Chrome, and sessions/scrape/screenshot/pdf plus external CDP client connections all worked with real results.

Installed repo deps and built api+ui; API runs in dev mode on 127.0.0.1:3000 with live Chrome; /v1/health=200; created sessions; scrape returned real example.com HTML; screenshot PNG decoded cleanly via ffmpeg; PDF valid with decompressed text streams; external puppeteer client connected over CDP and read page title; REPL printed real steel.dev title; production mode only fails for non-root because of hardcoded /files. UI dev server served 200; npm run dev -w api reached listening before a concurrent-instance user-data-dir conflict in my test.

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

Runsall runs of steel-browser

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.