open-browser-use tested by Argusic Runner

What the test found

The repo installs and builds in this container; the Go CLI/MCP/SDKs run and answer requests through a standing mock of the Chrome extension, and every test suite in the repo passes after the crypto fix.

No Chrome binary or extension in container, so end-to-end behavior was verified against a schema-correct mock of the extension's native messaging side speaking the wire protocol (4-byte LE length-prefixed JSON); real Chrome/Web Store integration could not be exercised. CLI, JS SDK, Python SDK, MCP, and action-run all round-tripped through the mock. Only repo change: webmcp.test.mjs crypto fix plus history entry.

Argusic installed open-browser-use in 14 minutes and launched it; verification reached Verified with mock services. 3 of 3 recorded errors were worked through (see the timeline below).

Runs with mocksall runs of open-browser-use

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.