Yes. plexo runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 6 errors on the way, and recorded the session.

How did Argusic test plexo?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5366a8c01c68. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test plexo?

The run that produced this verdict cost $1.38: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does plexo take to install?

4 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 plexo need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing plexo?

6 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.

Where is the evidence for plexo?

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.

plexo

Speed up downloads by combining multiple network connections in parallel

Runssource: GitHub homepageTypeScriptMITcommit 5366a8c01c68

TypeScript, MIT licensed. The project labels itself: bandwidth aggregation, cross platform, desktop app, downloader, downloadmanager, linux, macos and multiconnection.

plexo runs. An Argusic agent installed it in 4 minutes and hit 6 errors on a clean machine with no GPU, and the whole session was recorded.

Plexo installs and builds cleanly; the Electron app launches on the virtual display; the full Playwright suite runs with 284 passing, 20 environment-skips, and no deterministic failures after fixes were applied.
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 96.7 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 96.7 / 100
cost of the verifying run: $1.38 (measured)
recorded runs: 1
last tested: 2026-10-14
stars: 4,256
forks: 274
open issues: 32
watchers: 18
size: 3 MB
created: 2026-09-15
last push: 2026-10-14

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-14. 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 plexo, 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.

moved-file dialog test raced background history re-check (menu lost Show in folder, row label inconsistent)30 minutes
IPv6 disabled in container: 4 E2E tests failed with listen EADDRNOTAVAIL ::125 minutes
1 hedge timing flake under parallel load (2 KB/s crawl vs 400ms hedge)20 minutes
schedule datepicker: calendar popover animation made click unstable15 minutes
downloads-page tests: #panel-linux not visible (macOS tab selected for Mac UA)8 minutes
Electron chrome-sandbox SUID not configured in container3 minutes

Install time: 4 minutes
Cold machine to finish: 77 minutes
Errors hit and fixed: 6 hit, 5 fixed with no human help
How the result was proved: npm run test:e2e:smoke -> 83 passed 17 skipped; npx playwright test -> 284 passed 20 skipped; npx electron --version -> v44.4.4
Model tokens used: 6,320,639
Exact commit tested: 5366a8c01c68
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.

- `chrome-sandbox` SUID error — fix: `ELECTRON_DISABLE_SANDBOX=1`.
- downloads-page `#panel-linux summary not visible` — fix: select Linux tab first.
- schedule calendar `Go to the next month` unstable — fix: keyboard activation.
- `moved or deleted` rendering only when `isFinished(item)` — fix: use `'missing' in item`.
- moved-file right-click menu race — fix: branch on whether the menu still offers Show in folder.
**Final verified state**
- `npm run typecheck` OK; `npx electron --version` → `v44.4.4`.
- Targeted suite: 67/67 passed across the 4 previously-failing files.
- Full suite: 284 passed, 20 skipped (all 20 are documented environment/feature exclusions: 17 LAN-…
- Smoke suite: 83 passed, 17 skipped.
- One non-deterministic timing flake (hedge 2 KB/s race) reproduced 0/18 standalone, 1/284 in a par…
**Result line**

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 minutes.
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

Hit 6 errors during setup, 1 of which were not solved.
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 4 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 by	attempt	outcome	score	cost USD	when
Argusic Runner	1/3	Runs	96.67	1.38	2026-10-14 13:14 UTC

Topics (from GitHub)

bandwidth-aggregation cross-platform desktop-app downloader downloadmanager linux macos multiconnection parallel-downloads windows

Embed the badge

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

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

Questions

Does plexo run?: Yes. plexo runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test plexo?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5366a8c01c68. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test plexo?: The run that produced this verdict cost $1.38: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does plexo take to install?: 4 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 plexo need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing plexo?: 6 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.
Where is the evidence for plexo?: 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.