jira-cli runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.

How did Argusic test jira-cli?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 11ec3f844ab2. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test jira-cli?

The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does jira-cli take to install?

3 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 jira-cli need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing jira-cli?

Nothing did, in the recorded run: zero errors between clone and running.

Where is the evidence for jira-cli?

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.

jira-cli

🔥 Feature-rich interactive Jira command line.

Runs with mockssource: GitHubGoMITcommit 11ec3f844ab2

Go, MIT licensed. The project labels itself: atlassian, cli, cli app, command line, command line tool, console, go and golang.

jira-cli runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

The jira-cli binary is built, runs help/version commands without error, and all unit tests pass. Real Jira API credentials are required for operational commands.
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

verdict: Runs with mocks
Argusic Score: 92 / 100
cost of the verifying run: $0.02 (measured)
recorded runs: 2
last tested: 2026-09-16
stars: 5,985
forks: 416
open issues: 174
watchers: 36
size: 84 MB
created: 2020-11-22
last push: 2026-09-22

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-23. 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: 3 minutes
Cold machine to finish: 5 minutes
Errors hit and fixed: 0 hit, 0 fixed with no human help
How the result was proved: go test -race ./... exited 0 with 12 packages passed; ./jira version prints version string; ./jira --help prints usage
Model tokens used: 64,030
Exact commit tested: 11ec3f844ab2
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.

{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 3, "errors": [], "test_dep…
exec
/bin/sh -lc "cat /tmp/argusic_result.json | python3 -c \"
import json,sys
d=json.load(sys.stdin)
d['test_depth']='tier2_mock'
d['notes']='Go 1.26.5 was not installed in the container and had to be downloaded from go.dev. Buil…
print(json.dumps(d))\"" in /work/repo
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 3, "errors": [], "test_dep…
tokens used
64,030

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 3 minutes.
Nothing broke on the way: zero errors between clone and running.
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

Only reached a running state against stand-in services, so nothing here proves it works against the real ones.

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	2/3	Runs with mocks	92.00	0.02	2026-09-16 22:21 UTC
Argusic Runner	2/3	Runs with mocks	92.00	0.04	2026-09-03 14:50 UTC

Topics (from GitHub)

atlassian cli cli-app command-line command-line-tool console go golang golang-cli jira jira-cli made-in-nepal productivity productivity-tools terminal terminal-app tui

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

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

Questions

Does jira-cli run?: jira-cli runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test jira-cli?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 11ec3f844ab2. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test jira-cli?: The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does jira-cli take to install?: 3 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 jira-cli need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing jira-cli?: Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for jira-cli?: 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.