Yes. shelve runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 3 errors on the way, and recorded the session.

How did Argusic test shelve?

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

What did it cost to test shelve?

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 shelve take to install?

3.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 shelve need a GPU?

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

What goes wrong when installing shelve?

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.

Where is the evidence for shelve?

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.

shelve

Open-source secret & environment management. Secure, simple, collaborative. CLI & Github Sync

Runssource: GitHub homepageTypeScriptApache-2.0commit 377fdc8bd3b7

TypeScript, Apache-2.0 licensed. The project labels itself: cli, collaboration, developer experience, developer tools, env, environment variables, github and open source.

shelve runs. An Argusic agent installed it in 3.5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All 5 workspace packages build successfully, 158 tests pass (117 unit + 41 e2e), the Nuxt app serves HTTP 200 on port 3000, and the CLI binary responds to --help.
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.04 (measured)
recorded runs: 2
last tested: 2026-09-19
stars: 456
forks: 40
open issues: 17
watchers: 3
size: 62 MB
created: 2024-02-27
last push: 2026-09-17

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.

Time lost to each failure while testing shelve, 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.

Node.js v18.19.1 too old for pnpm 11.1.3 (needs >=22.13)2 minutes
pnpm not available initially, npm install -g failed due to permissions1 minute
Postinstall env validation failed due to missing NUXT_SESSION_PASSWORD and NUXT_PRIVATE_ENCRYPTION_KEY0.5 minutes

Install time: 4 minutes
Cold machine to finish: 12 minutes
Errors hit and fixed: 3 hit, 3 fixed with no human help
How the result was proved: pnpm build exited 0 with 5/5 packages built; vitest unit: 12 files, 117 passed; vitest e2e: 1 file, 41 passed; node apps/shelve/.output/server/index.mjs started and curl http://localhost:3000 returned 200; node packages/cli/dist/index.mjs --help printed usage
Model tokens used: 108,563
Exact commit tested: 377fdc8bd3b7
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 'export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && '"\\. \""'$NVM_DIR/nvm.sh"
export PATH="$HOME/.nvm/versions/node/v22.13.1/bin:$PATH"
cd /work/repo && kill %1 2>/dev/null; true' in /work/repo
 succeeded in 0ms:
All verified. Here's the summary:
2026-09-19T13:27:33.049908Z ERROR codex_core::session: failed to record rollout items: thread 01a0b…
2026-09-19T13:27:33.049959Z ERROR codex_core::session: failed to record rollout items: thread 01a0b…
tokens used
108,563
All verified. Here's the summary:

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.
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 Apache-2.0, as reported by its host.
Measured 2 times, so the result is not a one-off.

What did not, or is not known

Took 3.5 minutes to install, slower than the median of the 24 comparable projects Argusic has measured.

Of the 25 cli projects Argusic has installed and timed, shelve was the 15th fastest to reach a running state, and 23 of 25 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 3.5 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 by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Runs	100.00	0.04	2026-09-19 13:27 UTC
Argusic Runner	1/3	Runs	100.00	0.05	2026-09-05 20:51 UTC

Topics (from GitHub)

cli collaboration developer-experience developer-tools env environment-variables github open-source secrets secrets-management security self-hosted workflow

Embed the badge

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

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

Questions

Does shelve run?: Yes. shelve runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test shelve?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 377fdc8bd3b7. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test shelve?: 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 shelve take to install?: 3.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 shelve need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing shelve?: 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 shelve compare with the alternatives?: Of the 25 cli projects Argusic has installed and timed, shelve was the 15th fastest to reach a running state, and 23 of 25 reached one at all.
Where is the evidence for shelve?: 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.