gh-dash
A rich terminal UI for GitHub that doesn't break your flow.
Runs with mockssource: GitHubhomepageGoMITcommit 1b14dd961ea4
Go, MIT licensed. The project labels itself: bubbles, bubbletea, cli, cobra, gh extension, github, glamour and go.
gh-dash runs, with stand-ins for the services it depends on. An Argusic agent installed it in 5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The gh-dash binary builds from source, runs on Linux amd64, prints help and version output, and passes all 243 unit tests across 19 Go packages.
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 92 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.
- Install time
- 5 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- go test ./... passed with 243 PASS, 0 FAIL; go build . produced a 33 MB gh-dash binary; ./gh-dash --help printed usage; ./gh-dash -v printed version
- Model tokens used
- 569,280
- Exact commit tested
- 1b14dd961ea4
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Everything built and tested cleanly. Let me compose the final result exec /bin/sh -lc 'cd /work/repo && START_TIME=$(git log --all --oneline 2>/dev/null | head -1) ; echo "s… succeeded in 269ms: start time info present: 0 ---build ok--- ok github.com/dlvhdr/gh-dash/v4/internal/utils (cached) ---done--- All clear — the project builds, runs, and all 243 tests pass. Here's the result: tokens used 569,280 All clear — the project builds, runs, and all 243 tests pass. Here's the result:
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
- Installed in 5 minutes.
- Nothing broke on the way: zero errors between clone and running.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.18 |
Topics (from GitHub)
bubblesbubbleteaclicobragh-extensiongithubglamourgogolanglipglossterminaltui
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/gh-dash)Questions
- Does gh-dash run?
- gh-dash runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 5 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test gh-dash?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1b14dd961ea4. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test gh-dash?
- The run that produced this verdict cost $0.18: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does gh-dash take to install?
- 5 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 gh-dash need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing gh-dash?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for gh-dash?
- 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.