shell_gpt
A command-line productivity tool powered by AI large language models like GPT-5, will help you accomplish your tasks faster and more efficiently.
Runs with mockssource: GitHubPythonMITcommit a082bd5327ce
Python, MIT licensed. The project labels itself: chatgpt, cheat sheet, cli, commands, gpt 3, gpt 4, gpt 5 and linux.
shell_gpt runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.3 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
ShellGPT 1.5.1 installed in a Python venv; the test suite (29 tests across test_code, test_default, test_roles, test_shell) passes fully with mocked completions; the CLI entry point answers --help and --version.
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- System-level pip install blocked by externally-managed-environment (PEP 668)0.1 minutes
- Config module prompts for OpenAI API key on import, failing in headless/TTY-less environments0.1 minutes
- Config.get() raises UsageError on missing keys, hitting DEFAULT_TEMPERATURE at import time0.1 minutes
- Install time
- under a minute
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pytest tests -p no:warnings exited 0, 29 passed; sgpt --version returned 'ShellGPT 1.5.1'
- Model tokens used
- 66,045
- Exact commit tested
- a082bd5327ce
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
│ --role <str> System role for GPT model. │ │ --create-role <str> Create role. │ │ --show-role <str> Show role. │ │ --list-roles -lr List roles. │ ╰──────────────────────────────────────────────────────────────────────────────╯ All 29 tests pass, the CLI help works. Let me report the final result. exec /bin/sh -lc 'cd /work/repo && . venv/bin/activate && sgpt --version 2>&1' in /work/repo succeeded in 734ms: ShellGPT 1.5.1 tokens used 66,045
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 0.3 minutes, faster than the median of the 4 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.
- 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.
Of the 5 chatgpt projects Argusic has installed and timed, shell_gpt was the 1st fastest to reach a running state, and 2 of 5 reached one at all.
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.03 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.09 |
Topics (from GitHub)
chatgptcheat-sheetclicommandsgpt-3gpt-4gpt-5linuxllamallmollamaopenaiproductivitypythonshellterminal
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/shell-gpt)Questions
- Does shell_gpt run?
- shell_gpt runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 0 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test shell_gpt?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a082bd5327ce. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test shell_gpt?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does shell_gpt take to install?
- 0.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 shell_gpt need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing shell_gpt?
- 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 shell_gpt compare with the alternatives?
- Of the 5 chatgpt projects Argusic has installed and timed, shell_gpt was the 1st fastest to reach a running state, and 2 of 5 reached one at all.
- Where is the evidence for shell_gpt?
- 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.