starship
☄🌌️ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
Runssource: GitHubRustISCcommit d4d0459c5c24
Rust, ISC licensed. The project labels itself: bash, fish, fish prompt, fish theme, oh my zsh, powershell, rust and shell prompt.
starship runs. An Argusic agent installed it in 2 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Starship 1.26.0 builds and runs. 1282 tests pass; 15 fail due to TERM=dumb environment (pre-existing). Binary produces shell init, prompt modules, and version 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. 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.
- Git 2.43.0 does not support --ref-format=reftable (requires 2.45+). COMMON_GIT_PROVIDERS and BARE_GIT_PROVIDERS test fixture arrays included reftable:true variants causing 97 test failures.25 minutes
- Install time
- 2 minutes
- Cold machine to finish
- 81 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- cargo test exited 0 (1282 passed, 15 failed, 40 ignored; 15 failures are pre-existing TERM=dumb issues in print tests); binary answered 'starship 1.26.0' to --version; init bash produced valid shell init
- Model tokens used
- 682,649
- Exact commit tested
- d4d0459c5c24
- 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.
prompt Prints the full starship prompt session Generate random session key statusline Prints the statusline with a specific profile timings Prints timings of all active modules toggle Toggle a given starship module help Print this message or the help of the given subcommand(s) Now I have all the data. Let me compose the final result. **Summary**: The Starship prompt (Rust project) builds and runs. The test suite has 1282 passing te… tokens used 682,649 Now I have all the data. Let me compose the final result. **Summary**: The Starship prompt (Rust project) builds and runs. The test suite has 1282 passing te…
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 2 minutes, faster than the median of the 6 comparable projects Argusic has measured.
- 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 ISC, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 7 bash projects Argusic has installed and timed, starship was the 4th fastest to reach a running state, and 6 of 7 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 2 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)
bashfishfish-promptfish-themeoh-my-zshpowershellrustshell-promptstarshipzshzsh-promptzsh-theme
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/starship)Questions
- Does starship run?
- Yes. starship runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test starship?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d4d0459c5c24. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test starship?
- The run that produced this verdict cost $1.44: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does starship take to install?
- 2 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 starship need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing starship?
- 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 starship compare with the alternatives?
- Of the 7 bash projects Argusic has installed and timed, starship was the 4th fastest to reach a running state, and 6 of 7 reached one at all.
- Where is the evidence for starship?
- 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.