cogent
Apps made with Cogent Core
Runssource: GitHubhomepageGoBSD-3-Clausecommit 5db9d4415e5f
Go, BSD-3-Clause licensed. The project labels itself: application, apps, go, golang, graphics, gui, mail and text editor.
cogent runs. An Argusic agent installed it in 9 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
With user-local Go 1.27.3, X11/GL dev headers, and lavapipe Vulkan, the repo builds cleanly, its 4 tests pass, and the Cogent Marbles, Settings, and Task Manager desktop apps open real windows on the virtual display and stay running.
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.
- GUI build failed: wayland-client-core.h (and other X11/GL dev headers) missing4 minutes
- marbles/settings/taskmanager panicked in WebGPU surface init: no GPU adapter available3 minutes
- core setup requires sudo (sudo: command not found) to apt install system packages1 minute
- link failed: cannot find -lGL (no libGL.so symlink)1 minute
- Install time
- 9 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- go build -tags x11 ./... exited 0; go test -tags x11 -v ./... exited 0 with 4 passed, 0 failed; DISPLAY=:99 xwininfo -root -tree showed windows 'Cogent Marbles' 1024x640, 'Cogent Settings' 768x640, 'Cogent Task Manager' 916x480 with processes alive until timeout kill
- Model tokens used
- 290,850
- Exact commit tested
- 5db9d4415e5f
- 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.
- Installed Go 1.27.3 to `/tmp/go-install` (was not on PATH), ran `go mod download`, then `go insta… - `core setup` failed: it shells out to `sudo apt update` and there is no `sudo` in the container. … **Errors fixed** - `glfw` build failed missing `wayland-client-core.h` etc. Fixed by `apt-get download`ing the Ubunt… - Link failed `cannot find -lGL`. Fixed by symlinking runtime `libGL.so.1` (and other runtime `.so.… - GUI launch panicked in WebGPU surface init (`caps.Formats[0]` index out of range) because no Vulk… **Verification** - `go build -tags x11 ./...` exit 0. - `go test -tags x11 -v ./...` exit 0: 4 passed, 0 failed, 0 skipped (`code`, `terminal`, plus `ai`… **Apps launched** - `marbles` (Cogent Marbles) window `1024x640+128+80` seen via `xwininfo` after 7s, process alive u… - `settings` (Cogent Settings) window `768x640+256+80`; `taskmanager` (Cogent Task Manager) window …
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 9 minutes.
- Recovered from all 4 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 BSD-3-Clause, 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.
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 9 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
Topics (from GitHub)
applicationappsgogolanggraphicsguimailtext-editorvector-graphics
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cogent)Questions
- Does cogent run?
- Yes. cogent runs. Argusic installed and launched it on a clean machine in 9 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test cogent?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5db9d4415e5f. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test cogent?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does cogent take to install?
- 9 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 cogent need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing cogent?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for cogent?
- 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.