career-ops
Open-source AI job search: scan job portals, evaluate listings into a structured A-H report with a global 1-5 score, tailor your CV, track applications, runs locally in your AI coding CLI (Claude Code, Codex, OpenCode, Antigravity…)
Runssource: GitHubhomepageJavaScriptMITcommit 619a834dd786
JavaScript, MIT licensed. The project labels itself: ai agent, ai job search, ats, career, careerops, claude code, cli and cover letter.
career-ops runs. An Argusic agent installed it in 36 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
career-ops v1.30.0 installs and runs on Node v22.14.0 with Playwright chromium. Full test suite passes 7297/7297. Doctor reports normal fresh-setup warnings (cv.md, config/profile.yml, portals.yml missing). All core CLI tools operable.
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 97.3 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.
- Web test explore-ai-dedup.test.mjs crashed: cannot import .ts5 minutes
- npm postinstall failed: --with-deps tries su (no root)3 minutes
- node:sqlite unavailable (needs Node >=22.5)3 minutes
- Node v18 too old (need >=20 for Playwright)2 minutes
- validate-untrusted-content-coverage.mjs crashed: globSync missing1 minute
- Install time
- 36 minutes
- Cold machine to finish
- 35 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- node test-all.mjs exited 0 (7297 passed, 0 failed); npm install exited 0; doctor.mjs --json runs; stats.mjs, update-system.mjs check, generate-pdf.mjs --help all work.
- Model tokens used
- 183,122
- Exact commit tested
- 619a834dd786
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
5. **Web test `explore-ai-dedup.test.mjs`** imports `.ts` files directly without a loader. Fixed by… **Final state:** `node test-all.mjs` reports **7297 passed, 0 failed, 12 warnings** (warnings are e… tokens used 183,122 All 7297 tests pass, 0 failures. Here's the complete report: **Errors encountered & fixed:** 1. **Node.js too old** (v18.19.1 vs required >=20). Fixed by downloading Node v22.14.0 and setting … 2. **Playwright deps install failure** — `postinstall` script used `--with-deps` which calls `su` (… 3. **SQLite built-in not available** — `node:sqlite` requires Node >= 22.5. Fixed by upgrading to N… 4. **`validate-untrusted-content-coverage.mjs`** crashed — used `globSync` from `fs` which needs No… 5. **Web test `explore-ai-dedup.test.mjs`** imports `.ts` files directly without a loader. Fixed by… **Final state:** `node test-all.mjs` reports **7297 passed, 0 failed, 12 warnings** (warnings are e…
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 5 errors 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 3 times, so the result is not a one-off.
What did not, or is not known
- Took 36 minutes to install, slower than the median of the 36 comparable projects Argusic has measured.
Of the 37 ai projects Argusic has installed and timed, career-ops was the 37th fastest to reach a running state, and 30 of 37 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.
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
Topics (from GitHub)
ai-agentai-job-searchatscareercareeropsclaude-codeclicover-lettercvinterview-prepjob-applicationjob-huntingjob-searchjob-trackerjobsearchjobseekerslocal-firstopen-sourceresumeresume-builder
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/career-ops)Questions
- Does career-ops run?
- Yes. career-ops runs. Argusic installed and launched it on a clean machine in 36 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test career-ops?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 619a834dd786. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test career-ops?
- The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does career-ops take to install?
- 36 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 career-ops need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing career-ops?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does career-ops compare with the alternatives?
- Of the 37 ai projects Argusic has installed and timed, career-ops was the 37th fastest to reach a running state, and 30 of 37 reached one at all.
- Where is the evidence for career-ops?
- All 3 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.