starship

☄🌌️ The minimal, blazing-fast, and infinitely customizable prompt for any shell!

Runssource: GitHubhomepageRustISCcommit 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 7 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The starship prompt builds, prints its version (1.26.0), renders a prompt string, and 1295 of 1297 tests pass, only two pre-existing flaky stash tests fail intermittently.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.15 (measured)
recorded runs
2
last tested
stars
60,799
forks
2,944
open issues
1,068
watchers
197
size
46 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.

Time lost to each failure while testing starship, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Git 2.43 does not support --ref-format=reftable (requires git >=2.45), causing all reftable test fixtures to silently fail (git clone exits 129 with unknown option error)4 minutes
  • shows_stashed and shows_stashed_with_count_unless_reftable tests are flaky: git stash --all does not reliably create stashes on git 2.43 in this container environment1 minute
  • TERM=dumb causes get_prompt() to return "Starship disabled" early0.5 minutes
Install time
7 minutes
Cold machine to finish
30 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
cargo test (1295 passed, 2 failed, 40 ignored); ./target/debug/starship --version printed 'starship 1.26.0' with build info; ./target/debug/starship prompt printed prompt output
Model tokens used
630,128
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.

exec
/bin/sh -lc 'echo "Start time (rustup install): ~28 seconds" && echo "Build time: 2m 01s" && echo "…
 succeeded in 0ms:
Start time (rustup install): ~28 seconds
Build time: 2m 01s
Test time (first run): 24s
Fix + verify time: ~3 minutes
Total: ~6 minutes
Let me compile the final report. The 2 remaining failures (`shows_stashed`, `shows_stashed_with_cou…
tokens used
630,128
Let me compile the final report. The 2 remaining failures (`shows_stashed`, `shows_stashed_with_cou…

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 7 minutes, faster than the median of the 11 comparable projects Argusic has measured.
  • 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 ISC, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 12 bash projects Argusic has installed and timed, starship was the 6th fastest to reach a running state, and 9 of 12 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 7 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.15
Argusic Runner1/3Runs100.001.44

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.

[![Tested by Argusic](https://argusic.com/badge/starship.svg)](https://argusic.com/subject/starship)

Questions

Does starship run?
Yes. starship runs. Argusic installed and launched it on a clean machine in 7 minutes, hitting 3 errors 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. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test starship?
The run that produced this verdict cost $0.15: 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?
7 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?
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 starship compare with the alternatives?
Of the 12 bash projects Argusic has installed and timed, starship was the 6th fastest to reach a running state, and 9 of 12 reached one at all.
Where is the evidence for starship?
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