claude-powerline
Beautiful vim-style powerline for Claude Code
Runssource: GitHubhomepageTypeScriptMITcommit 9e9b17f9c05b
TypeScript, MIT licensed. The project labels itself: claude code, cli, developer tools, git, lightweight and statusline.
claude-powerline runs. An Argusic agent installed it in 20 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 414 tests pass, all 4 display styles (minimal/powerline/capsule/tui) render correctly, binary builds via esbuild, npm run build produces dist/index.mjs and dist/browser.js
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.5 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.
- Build tool tsdown requires Node >=20.19.0 but container has Node 18.19.15 minutes
- core.test.ts: NO_COLOR=1 and TERM=dumb in container cause getColorSupport() to return 'none', so no ANSI escape codes in output3 minutes
- colors.test.ts: after clearing env, tty.hasColors() returns false headless, getColorSupport() returns 'none'2 minutes
- Install time
- 20 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npm test exited 0, 414 tests passed, 17 suites all green; echo JSON | node bin/claude-powerline --style=powerline outputs correctly formatted statusline segments for all 4 styles
- Model tokens used
- 142,753
- Exact commit tested
- 9e9b17f9c05b
- 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.
D $0.00 (0 tokens) R active C 0 (100%) succeeded in 7182ms: Test Suites: 17 passed, 17 total Tests: 414 passed, 414 total Snapshots: 11 passed, 11 total Time: 6.17 s Ran all test suites. Now I have everything I need for the final report. tokens used 142,753 Now I have everything I need for the final report.
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 3 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 2 times, so the result is not a one-off.
What did not, or is not known
- Took 20 minutes to install, slower than the median of the 21 comparable projects Argusic has measured.
Of the 22 claude-code projects Argusic has installed and timed, claude-powerline was the 21st fastest to reach a running state, and 22 of 22 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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/claude-powerline)Questions
- Does claude-powerline run?
- Yes. claude-powerline runs. Argusic installed and launched it on a clean machine in 20 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test claude-powerline?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9e9b17f9c05b. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test claude-powerline?
- The run that produced this verdict cost $0.22: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does claude-powerline take to install?
- 20 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 claude-powerline need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing claude-powerline?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does claude-powerline compare with the alternatives?
- Of the 22 claude-code projects Argusic has installed and timed, claude-powerline was the 21st fastest to reach a running state, and 22 of 22 reached one at all.
- Where is the evidence for claude-powerline?
- 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.