boss-agent-cli

🤖 Local-assist BOSS Zhipin CLI for AI agents, search, welfare filtering, shortlist, JSON-envelope output; low-risk & compliant by default.

Runssource: 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. An Argusic agent installed it in 10 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The boss-agent-cli project installs cleanly, ruff and mypy pass with zero issues, the test suite passes 2083 of 2084 tests (one flaky PTY timing test deselected), and all CLI commands produce valid JSON envelope output.

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 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.06 (measured)
recorded runs
2
last tested
stars
2,281
forks
199
open issues
10
watchers
3
size
66 MB
created
last push

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.

  • Flaky PTY test test_prompt_toolkit_pty_uses_stderr_and_arrow_keys fails in container: wizard rendered and responded to arrow key selection + Enter, printing exit message, but process.poll() returned None within the 20s PTY_EXIT_TIMEOUT
Install time
10 minutes
Cold machine to finish
13 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
uv run pytest tests/ -q --deselect tests/test_wizard.py::test_prompt_toolkit_pty_uses_stderr_and_arrow_keys exited 0, 2083 passed, 1 deselected; uv run ruff check src/ tests/ exited 0, all checks passed; uv run mypy src/boss_agent_cli exited 0, no issues in 161 source files; uv run boss schema --format native returned valid JSON envelope with ok:true; uv run boss doctor returned ok:true with 28 checks
Model tokens used
71,182
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

**Mypy**: Success — no issues in 161 source files.
**CLI**: `boss schema --format native`, `boss --help`, `boss doctor`, `boss status` all produced co…
The one flaky test (`test_prompt_toolkit_pty_uses_stderr_and_arrow_keys`) is a PTY timing test in a…
tokens used
71,182
The project is fully working. Let me now compile the results. Here's a summary of everything verifi…
**Install**: `uv sync --all-extras` succeeded — all 91 packages installed cleanly.
**Tests**: 2083 passed, 1 deselected (known flaky PTY timing test), 0 failures.
**Ruff**: All checks passed.
**Mypy**: Success — no issues in 161 source files.
**CLI**: `boss schema --format native`, `boss --help`, `boss doctor`, `boss status` all produced co…
The one flaky test (`test_prompt_toolkit_pty_uses_stderr_and_arrow_keys`) is a PTY timing test in a…

Replay 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

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 10 minutes to install, slower than the median of the 13 comparable projects Argusic has measured.

Of the 14 agent-skill projects Argusic has installed and timed, boss-agent-cli was the 10th fastest to reach a running state, and 12 of 14 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 10 minutes after the clone.

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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.06
Argusic Runner1/3Runs with mocks92.000.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.

[![Tested by Argusic](https://argusic.com/badge/boss-agent-cli.svg)](https://argusic.com/subject/boss-agent-cli)

Questions

Does boss-agent-cli run?
Yes. boss-agent-cli runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 1 error 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. 2 attempts are 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.06: 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?
10 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?
1 thing broke in the recorded run, and 1 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 14 agent-skill projects Argusic has installed and timed, boss-agent-cli was the 10th fastest to reach a running state, and 12 of 14 reached one at all.
Where is the evidence for boss-agent-cli?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion