gooey-pi

Desktop workspace for Pi, OMP, and Prime Agent

Runssource: GitHubhomepageTypeScriptMITcommit 459c99656904

TypeScript, MIT licensed. The project labels itself: coding agents, developer tools, electron, linux, macos, oh my pi, pi and prime agent.

gooey-pi runs. An Argusic agent installed it in 1.5 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

GooeyPi builds, all 165 vitest unit test files pass (1927/1928 tests), and all 66 Playwright Electron e2e tests complete with 63 passed, 0 failed, 3 macOS-specific skipped.

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.33 (measured)
recorded runs
2
last tested
stars
981
forks
86
open issues
12
watchers
4
size
73 MB
created
last push

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.

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

  • zsh not installed in container; test environment set SHELL=/bin/zsh which doesn't exist, causing 'shell is not executable' errors in terminal tests15 minutes
  • Test expected 'Startup & background' heading which is macOS-only (conditional on platform === 'darwin')3 minutes
  • Pixel-rounding differences under xvfb caused resize tests to fail with tighter tolerances3 minutes
  • Tests used macOS keyboard shortcut symbol (⌘N) which displays as Ctrl+N on Linux2 minutes
  • Test expected terminal tab name 'zsh 1' but shell is now bash1 minute
Install time
2 minutes
Cold machine to finish
72 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
npm test exited 0 (165 test files, 1927 passed, 1 skipped). xvfb-run -a npx playwright test exited 0 (63 passed, 0 failed, 3 skipped on macOS-only features).
Model tokens used
407,104
Exact commit tested
459c99656904
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.

     await expect(page.locator('.terminal-surface:not([hidden]) .xterm-rows')).toContainText('first…
     const geometry = await page.evaluate(() => {
Clean diff. Let me now finalize the result.
exec
/bin/sh -lc '# Total time check
echo "Install started around the beginning of this session"
echo "Let me compile the result"' in /work/repo
 succeeded in 0ms:
Install started around the beginning of this session
Let me compile the result
tokens used
407,104

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 1.5 minutes, faster than the median of the 3 comparable projects Argusic has measured.
  • Recovered from all 5 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 2 times, so the result is not a one-off.

Of the 4 coding-agents projects Argusic has installed and timed, gooey-pi was the 2nd fastest to reach a running state, and 3 of 4 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 1.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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.33
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

coding-agentsdeveloper-toolselectronlinuxmacosoh-my-pipiprime-agentwindows

Embed the badge

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

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

Questions

Does gooey-pi run?
Yes. gooey-pi runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test gooey-pi?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 459c99656904. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test gooey-pi?
The run that produced this verdict cost $0.33: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does gooey-pi take to install?
1.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 gooey-pi need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing gooey-pi?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does gooey-pi compare with the alternatives?
Of the 4 coding-agents projects Argusic has installed and timed, gooey-pi was the 2nd fastest to reach a running state, and 3 of 4 reached one at all.
Where is the evidence for gooey-pi?
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.

Discussion