ccstatusline
🚀 Beautiful highly customizable statusline for Claude Code CLI with powerline support, themes, and more.
Runssource: GitHubTypeScriptMITcommit 68eb01e40d0e
TypeScript, MIT licensed. The project labels itself: ai tools, claude code, cli, developer tools, git, powerline, statusbar and statusline.
ccstatusline runs. An Argusic agent installed it in 6 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Dependencies installed, project builds to dist/ccstatusline.js, all 1897 tests pass, and piped JSON input renders a formatted status line with model name and git info.
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 100 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.
- bun: not found2 minutes
- npm ERESOLVE peer dependency conflict with eslint-plugin-react1 minute
- TypeScript errors in git-review-cache.test.ts readFileSync overload assignment1 minute
- ESLint 10.x crashes on Node 18 (util.styleText not a function)
- Install time
- 6 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- bun test exited 0 (1897 passed, 3732 expect calls); node dist/ccstatusline.js with piped JSON input produced correct status line output; bun run build succeeded bundling 851 modules
- Model tokens used
- 208,020
- Exact commit tested
- 68eb01e40d0e
- 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.
**Timeline**: ~6 minutes total. **Install**: Dependencies installed with `npm install --legacy-peer-deps` (needed to bypass a peer-… **Build**: `bun run build` succeeded — 851 modules bundled, 2.94 MB output, version placeholder rep… **Tests**: `bun test` — **1897 pass, 0 fail, 3732 expect() calls** across 135 files. **Errors encountered**: | Error | Fix | Time | |---|---|---| | `bun: not found` — Bun not in container PATH | Installed bun via `npm install -g --prefix ~/.loca… | `npm ERESOLVE` — [email protected] peer-dep conflict with ESLint 10 | `npm install --leg… | TS errors in `git-review-cache.test.ts` — readFileSync overload not assignable to simplified arro… | ESLint `util.styleText is not a function` — ESLint 10.x needs Node >= 20, container has Node 18 |… **Verification**: `echo '{"model":{"id":"gpt-4"}}' | node dist/ccstatusline.js` printed `Model: gpt…
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.
- Installed in 6 minutes.
- Recovered from all 4 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.
Of the 4 ai-tools projects Argusic has installed and timed, ccstatusline was the 2nd fastest to reach a running state, and 3 of 4 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 6 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
Topics (from GitHub)
ai-toolsclaude-codeclideveloper-toolsgitpowerlinestatusbarstatuslineterminalthemeing
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ccstatusline)Questions
- Does ccstatusline run?
- Yes. ccstatusline runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test ccstatusline?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 68eb01e40d0e. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test ccstatusline?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ccstatusline 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 ccstatusline need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ccstatusline?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does ccstatusline compare with the alternatives?
- Of the 4 ai-tools projects Argusic has installed and timed, ccstatusline was the 2nd fastest to reach a running state, and 3 of 4 reached one at all.
- Where is the evidence for ccstatusline?
- 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.