huashu-chrome tested by Argusic Runner

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

all runs of huashu-chromeai-agentsbrowser-automationchrome-extensionclaude-codecodexcursor

Session recording

Loading recording...

Download the original recording · fingerprint 7f18fc2b44e1afcb...

What the test found

All 123 unit tests pass, npm install completes, MCP server responds with 22 tools, bridge daemon starts and answers probes, doctor command runs successfully.

Node v18.19.1 is below the >=20 requirement but npm install succeeded with only engine warnings. All 123 tests pass. MCP server responds with 22 tools. Bridge starts and runs. Doctor command works but reports no Chrome extension connected (expected in headless container). One-line import fix applied for WebSocket reference.

Argusic installed huashu-chrome in 0.5 minutes and launched it; verification reached Verified running for real. 1 of 1 recorded error was worked through (see the timeline below).

Runsall runs of huashu-chrome

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