inshellisense
IDE style command line auto complete
Runssource: GitHubTypeScriptMITcommit 63872c52ebc8
TypeScript, MIT licensed. The project labels itself: autocomplete, bash, cli, fish, linux, macos, nushell and powershell.
inshellisense runs. An Argusic agent installed it in 8 minutes and hit 2 errors on a clean machine with no GPU, and the whole session was recorded.
inshellisense 0.0.4 on Node 18.19.1 builds, installs, runs doctor, and provides shell autocompletions via the complete command and passes all unit tests; e2e UI tests skipped due to native binary dependency requiring Node >=20
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 90 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.
- node:sea static import fails on Node 184 minutes
- @microsoft/tui-test requires Node >=20 for native binary2 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 2 hit, 1 fixed with no human help
- How the result was proved
- npm test: 14 suites passed, 202 tests passed, 93 snapshots passed; node build/index.js complete 'git sta' returned valid JSON with 3 completions
- Model tokens used
- 44,840
- Exact commit tested
- 63872c52ebc8
- 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.
Here's the summary of everything I did and found: **Install**: `npm install` succeeded. `npm run build` (tsc) succeeded. **Errors found & fixed**: 1. **`node:sea` missing on Node 18** — the `import sea from "node:sea"` static import fails because… 2. **`@microsoft/tui-test` native binary** — this test tool requires Node >= 20 for its napi-rs bin… **Verification**: - `npm test` — **14/14 test suites pass**, 202 tests pass, 93 snapshots pass. 1 suite (e2e) skipped… - `node ./build/index.js -v` — prints `__VERSION__` (placeholder, substituted at pack time). - `node ./build/index.js --help` — prints usage. - `node ./build/index.js doctor` — reports installation healthy. - `node ./build/index.js complete "git sta"` — returns JSON with `stage`, `status`, `stash` suggest… - `node ./build/index.js reinit` — installs resources successfully.
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 8 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Hit 2 errors during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 8 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)
autocompletebashclifishlinuxmacosnushellpowershellpwshterminalwindowsxonshzsh
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/inshellisense)Questions
- Does inshellisense run?
- Yes. inshellisense runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test inshellisense?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 63872c52ebc8. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test inshellisense?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does inshellisense take to install?
- 8 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 inshellisense need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing inshellisense?
- 2 things broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for inshellisense?
- 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.