boss-agent-cli tested by Argusic Runner

Attempt 1 of 3 · Runs with mocks · Argusic Score 92.0 of 100

all runs of boss-agent-cliagent-skillagent-toolsai-agentboss-zhipinclaudecli

Session recording

Loading recording...

Download the original recording · fingerprint 7a379fd303ee166f...

What the test found

The project installs and builds under uv, the whole offline test suite passes 2084/2084, ruff and mypy pass, the boss CLI and the MCP server start and answer, and the CLI's status, detail, search, welfare-filter and wizard commands return correct ok:true JSON envelopes against a local mock of the zhipin API that mirrors the repo's own documented response schema.

Real zhipin login required for live platform data; instead stood up a local HTTP mock (127.0.0.1:18888/18889) of the zhipin API with the envelope the app itself validates in tests, and a sitecustomize shim redirected the CLI's base_url and the headless browser home page to it. Through that mock, the installed CLI search/welfare/detail paths return real JSON envelopes: `status --live` ok:true logged_in:true user:Mock 用户, `detail` ok:true with title Golang 工程师, `search --welfare 双休` ok:true 1 item with welfare_match, `wizard job_search` completed. Whole-run pytest: 2084 passed. Only mock/lab rigging was added under /tmp; the repository is unchanged (git status clean).

Argusic installed boss-agent-cli in 6 minutes and launched it; verification reached Verified with mock services. 2 of 2 recorded errors were worked through (see the timeline below).

Runs with mocksall runs of boss-agent-cli

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