pstop
htop for Windows . TUI system monitor with per-core CPU bars, memory/swap/network, tree view, process kill, 7 color schemes, mouse support. cargo install pstop
Could not verifysource: GitHubhomepageRustMITcommit 8f6a1bc684b1
Rust, MIT licensed. The project labels itself: cli, htop, htop alternative, htop for windows, powershell, process manager, process viewer and ratatui.
Argusic could not get pstop running. An Argusic agent installed it in 37 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Project cross-compiles to valid Windows PE32+ console binaries (pstop.exe and htop.exe) using x86_64-pc-windows-gnullvm target; source compiles without warnings; binaries cannot execute in this Linux container because the installed wine lacks required Windows DLLs (zlib1.dll, full shell32/user32 stubs).
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 31.7 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.
- Windows-only crate requires Windows target with MSVC linker unavailable (no link.exe)25 minutes
- Cannot run Windows executable without Wine; wine requires missing DLL (zlib1.dll) and full prefix setup8 minutes
- Rust toolchain not installed on system2 minutes
- Install time
- 37 minutes
- Cold machine to finish
- 41 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- cargo build --release --target x86_64-pc-windows-gnullvm exited 0, produced valid PE32+ Windows CUI executables (verified via objdump -p showing Subsystem 00000003 Windows CUI); cargo check --target x86_64-pc-windows-msvc exited 0; cargo test --no-run built all test executables. Binary execution under wine failed with 'could not load kernel32.dll' / 'unimplemented function shell32.dll.SHGetFolderPathW' due to incomplete wine DLL set.
- Model tokens used
- 3,844,882
- Exact commit tested
- 8f6a1bc684b1
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- Downloaded mingw-w64 import libraries from Ubuntu packages (extracted without root/sudo) - Created Rust stubs for missing MinGW CRT symbols (`mainCRTStartup`, `atexit`) - Configured LLD linker from the Rust toolchain to produce PE binaries 4. Built both debug and release configurations with 0 warnings and 0 errors **Binaries produced:** - `pstop.exe` (235 KB, release) - main system monitor - `htop.exe` (229 KB, release) - identical binary with alternative name - Both confirmed as valid PE32+ Windows CUI executables via `objdump -p` **Verification attempts:** - Wine was installed from Ubuntu packages to attempt execution, but the installed wine version lack… - All compile-time verification passes: `cargo check` (MSVC target), `cargo build` (GNU target), an… **Result:** The project cross-compiles successfully. To actually run it, you need a Windows system …
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
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
- Took 37 minutes to install, slower than the median of the 127 comparable projects Argusic has measured.
Of the 128 cli projects Argusic has installed and timed, pstop was the 127th fastest to reach a running state, and 117 of 128 reached one at all.
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 | 2/3 | Did not run | 50.00 | 0.93 | |
| Argusic Runner | 1/3 | Did not run | 13.33 | 0.25 |
Topics (from GitHub)
clihtophtop-alternativehtop-for-windowspowershellprocess-managerprocess-viewerratatuirustsystem-monitortask-managerterminaltoptuiwindowswindows-terminal
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/pstop)Questions
- Does pstop run?
- Argusic could not verify that pstop runs. Argusic installed and launched it on a clean machine in 37 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test pstop?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8f6a1bc684b1. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test pstop?
- The run that produced this verdict cost $0.93: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does pstop take to install?
- 37 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 pstop need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing pstop?
- 3 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 pstop compare with the alternatives?
- Of the 128 cli projects Argusic has installed and timed, pstop was the 127th fastest to reach a running state, and 117 of 128 reached one at all.
- Where is the evidence for pstop?
- 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.