boss-agent-cli
🤖 Local-assist BOSS Zhipin CLI for AI agents, search, welfare filtering, shortlist, JSON-envelope output; low-risk & compliant by default.
Runs with mockssource: GitHubhomepagePythonMITcommit cf38175d11a1
Python, MIT licensed. The project labels itself: agent skill, agent tools, ai agent, boss zhipin, claude, cli, command line and job hunting.
boss-agent-cli runs, with stand-ins for the services it depends on. An Argusic agent installed it in 6 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
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.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Fresh environment had no uv; `pip install uv` then `uv sync --all-extras` installed all deps cleanly, but the plain README flow ran into an unrelated missing-dependency problem at the installed entry point: `boss-mcp --help` failed with `ModuleNotFoundError: No module named 'mcp'`.2 minutes
- Patchright chromium was missing, so `doctor` warned and browser-channel commands fail.1 minute
- Install time
- 6 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- uv run pytest tests/ -q: 2084 passed; uv run ruff check src/ tests/: All checks passed; uv run mypy src/boss_agent_cli: Success (161 files); uv run boss --version: boss, version 2.0.0; uv run boss schema --format native / uv run boss doctor: JSON envelope with ok:true; boss-mcp --help: usage printed; against a schema-correct mock, CLI status/detail/search/wizard commands returned ok:true with expected data.
- Model tokens used
- 1,730,084
- Exact commit tested
- cf38175d11a1
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
await server.run(read_stream, write_stream, server.create_initialization_options())
def _normalize_path(path: str) -> str:
if not path.startswith("/"):
return f"/{path}"
return path
Now I have all the information needed. Let me compile the final result.
exec
/bin/sh -lc 'rg -c "''^from boss_agent_cli|''^import boss_agent_cli" /tmp/mockboss/sitecustomize.py…
succeeded in 0ms:
6
tokens used
1,730,084Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 6 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 agent-skill projects Argusic has installed and timed, boss-agent-cli was the 4th fastest to reach a running state, and 2 of 4 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.34 |
Topics (from GitHub)
agent-skillagent-toolsai-agentboss-zhipinclaudeclicommand-linejob-huntingjob-searchmcpmodel-context-protocolpythonrecruiter-workflowrecruitmentresumezhipin
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/boss-agent-cli)Questions
- Does boss-agent-cli run?
- boss-agent-cli runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 6 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test boss-agent-cli?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit cf38175d11a1. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test boss-agent-cli?
- The run that produced this verdict cost $0.34: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does boss-agent-cli take to install?
- 6 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does boss-agent-cli need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing boss-agent-cli?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does boss-agent-cli compare with the alternatives?
- Of the 4 agent-skill projects Argusic has installed and timed, boss-agent-cli was the 4th fastest to reach a running state, and 2 of 4 reached one at all.
- Where is the evidence for boss-agent-cli?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.