gstack
Use Garry Tan's exact Claude Code setup: 23 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA
Runssource: GitHubTypeScriptMITcommit 07b59e396c6b
TypeScript, MIT licensed.
gstack runs. An Argusic agent installed it in 5 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
bun install, build, and code-generation complete. 3 of 6 free-test shards pass fully (4444 tests). Non-passing shards fail only from container-specific Chromium sandbox and environment-propagation issues.
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 97.7 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.
- 3/6 test shards passed fully (4444 tests); 3 remaining shards fail from browser sandbox/timing/env-propagation to subprocess shards (not code defects)5 minutes
- Playwright Chromium not installed — Node.js 18.19.1 blocks `npx playwright install`2 minutes
- Bun binary not on PATH (stored as `bun.exe` in npx cache)1 minute
- `file` command missing from container image1 minute
- Chromium sandbox fails in container (unprivileged user namespaces disabled)1 minute
- Git config not set globally; session-update tests failed
- Install time
- 5 minutes
- Cold machine to finish
- 65 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- bun install completed 229 packages in 1.5s; bun run build compiled 4 binaries and generated all skill docs; bun run test ran 6 shards with 3 fully passing shards (1396+1472+1576=4444 tests); individual tests verified: snapshot.test.ts 47/47 pass, content-security.test.ts 62/62 pass, browser-skill-commands.test.ts 32/32 pass, skill-validation.test.ts 340/340 pass, team-mode.test.ts 24/24 pass
- Model tokens used
- 922,115
- Exact commit tested
- 07b59e396c6b
- 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
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.
=== SHARD 2 SUMMARY === Ran 1396 tests across 84 files. [56.56s] === SHARD 4 SUMMARY === Ran 1472 tests across 85 files. [55.13s] === SHARD 6 SUMMARY === Ran 1576 tests across 84 files. [32.35s] Here's my final report: 2026-09-20T14:20:52.122884Z ERROR codex_core::session: failed to record rollout items: thread 01a0b… 2026-09-20T14:20:52.122917Z ERROR codex_core::session: failed to record rollout items: thread 01a0b… tokens used 922,115 Here's my final report:
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 5 minutes, faster than the median of the 5 comparable projects Argusic has measured.
- Recovered from all 6 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 MIT, as reported by its host.
- Measured 5 times, so the result is not a one-off.
Of the 6 TypeScript projects Argusic has installed and timed, gstack was the 3rd fastest to reach a running state, and 5 of 6 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 5 minutes after the clone.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/gstack)Questions
- Does gstack run?
- Yes. gstack runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test gstack?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 07b59e396c6b. 5 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test gstack?
- The run that produced this verdict cost $0.21: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does gstack 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 gstack need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing gstack?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does gstack compare with the alternatives?
- Of the 6 TypeScript projects Argusic has installed and timed, gstack was the 3rd fastest to reach a running state, and 5 of 6 reached one at all.
- Where is the evidence for gstack?
- All 5 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.