mygo
Develop desktop apps with native UI or web frontend in Go
Runssource: GitHubhomepageGoMITcommit b0604652c0e9
Go, MIT licensed.
mygo runs. An Argusic agent installed it in 4.3 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The repository builds, vets, and tests across all platforms (linux, windows, wasm), runs 223/223 JS tests, produces a 9.2 MB release-sized native UI binary, and the CLI (version 0.7.3) generates TypeScript clients.
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
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.
- No GPU render node (/dev/dri/renderD*): AST display-only DRM driver, no 3D
- WebKitGTK (libwebkit2gtk-4.1.so.0) not installed
- Install time
- 4 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- go test ./... exited 0 (all suites pass); bun run test exited 0 (223/223 pass); mygo version printed 'mygo 0.7.3'; counter-native binary launched on DISPLAY=:99, printed diagnostic, entered GTK event loop; go build and go vet pass for native, linux, windows, wasm, and mygo_noinspector; mygo generate wrote TypeScript client for todo example
- Model tokens used
- 190,004
- Exact commit tested
- b0604652c0e9
- 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 attempt that decided the verdict above. 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.
2026-11-01T07:27:38.716409Z ERROR codex_core::session: failed to record rollout items: thread 01a19… tokens used 190,004 Here's my final assessment. **Installation**: mise installed Go 1.27.3 and Bun 1.4.4 from the repo's `mise.toml`. `go build ./.… **Go tests**. `go test ./...` passes all suites -- the core, the fake-backend tests, `internal/gpu/… **Desktop launch**: The native UI counter app (`/tmp/counter-native`, 9.2 MB stripped binary) start… **CLI**: `mygo version` returns `mygo 0.7.3`. `mygo generate examples/todo` regenerates the TypeScr… **Errors**: - No GPU render device (`/dev/dri/renderD*` absent, only an AST display controller), so native UI G… - WebKitGTK (`libwebkit2gtk-4.1.so.0`) is not installed, so webview apps can't open windows. Both are expected in a container without root; the app prints clear diagnostics in each case.
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 4.3 minutes, faster than the median of the 4 comparable projects Argusic has measured.
- Recovered from all 2 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 5 Go projects Argusic has installed and timed, mygo was the 3rd fastest to reach a running state, and 4 of 5 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 4.3 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/mygo)Questions
- Does mygo run?
- Yes. mygo runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test mygo?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b0604652c0e9. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test mygo?
- 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 mygo take to install?
- 4.3 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 mygo need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mygo?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does mygo compare with the alternatives?
- Of the 5 Go projects Argusic has installed and timed, mygo was the 3rd fastest to reach a running state, and 4 of 5 reached one at all.
- Where is the evidence for mygo?
- 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.