grasp
Grasp helps you manage multiple projects and parallel coding agents in one visual workflow, so humans can understand faster and ship more.
Runssource: GitHubTypeScriptMITcommit 796b6f297992
TypeScript, MIT licensed. The project labels itself: agent, ai, browser automation, harness, harness ai, harness ci, harness design and harness engineering.
grasp runs. An Argusic agent installed it in 17 minutes and hit 5 errors on a clean machine with no GPU, and the whole session was recorded.
With user-local Go 1.27.3 and Node 24.12.0, the built Grasp server and gateway binaries start and answer health 200, admin login and project APIs return 200 with seeded data, and the server, web, docs, gateway, and sandbox build, test, and coverage suites all pass.
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.
- go not found in container; server module requires Go 1.25+3 minutes
- node v18.19.1 present but web CI requires Node 242 minutes
- first server launch used wrong env name GRASP_SERVER_PORT and listened on 80801 minute
- docker and docker compose not found; default README ./start.sh stack cannot run without root
- server logs warn on boot: sql converting argument $1 type: unsupported type models.ProjectNotifyPolicy (notify policy channelIds backfill failed)
- Install time
- 17 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 5 hit, 3 fixed with no human help
- How the result was proved
- curl -sS http://127.0.0.1:18080/api/health returned 200 with status ok; POST /api/auth/login admin/demo1234 returned 200; GET /api/auth/me returned 200 admin; GET /api/projects returned 200 with seeded default project; gateway curl http://127.0.0.1:18899/healthz returned 200; go test ./... passed in server, gateway, and sandbox; vitest run reported 3636 passed, 8 skipped; npm run build and npm run build in docs both exited 0
- Model tokens used
- 400,836
- Exact commit tested
- 796b6f297992
- 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.
2026-10-22T05:23:44.361267Z ERROR codex_core::session: failed to record rollout items: thread 01a16…
2026-10-22T05:23:44.361305Z ERROR codex_core::session: failed to record rollout items: thread 01a16…
tokens used
400,836
**Final report**
All module-level install/build/test/launch work was verified with user-local toolchains. Container …
- Server: build, vet, all packages `go test` ok; gen-configdoc check ok; coverage 90.7% ≥ 90; launc…
- Web: `npm ci`, `vue-tsc --noEmit` exit 0, ESLint 0 errors, `vitest run` 3636 passed / 8 skipped (…
- Docs: `npm run build` → public/ generated.
- Gateway Go: build/vet/tests ok, coverage 90.9% ≥ 90; launched binary → `/healthz` 200 `{"driver":…
- Sandbox Go: build/vet/tests ok, coverage 96.6% ≥ 90; `bash -n` on all scripts ok; `test-inject.sh…
- Recorded but unfixed: runtime log warning `notify policy channelIds backfill failed: unsupported …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.
- 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
- Took 17 minutes to install, slower than the median of the 140 comparable projects Argusic has measured.
- Hit 5 errors during setup, 2 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 141 agent projects Argusic has installed and timed, grasp was the 118th fastest to reach a running state, and 94 of 141 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.
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)
agentaibrowser-automationharnessharness-aiharness-ciharness-designharness-engineeringharness-execution-layerharness-frameworkllmmutli-agentworkflowworkflow-automation
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/grasp)Questions
- Does grasp run?
- Yes. grasp runs. Argusic installed and launched it on a clean machine in 17 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test grasp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 796b6f297992. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test grasp?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does grasp take to install?
- 17 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 grasp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing grasp?
- 5 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 grasp compare with the alternatives?
- Of the 141 agent projects Argusic has installed and timed, grasp was the 118th fastest to reach a running state, and 94 of 141 reached one at all.
- Where is the evidence for grasp?
- 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.