pueue
:stars: Manage your shell commands.
Runssource: GitHubRustApache-2.0commit b3a2077ddc57
Rust, Apache-2.0 licensed. The project labels itself: command line, command line tool, daemon, hacktoberfest, queue manager, queue tasks, rust and shell queue.
pueue runs. An Argusic agent installed it in 14 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Pueue daemon and client build, all 128 tests pass, and the full add/status/log workflow runs correctly.
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.
- Snapshot tests `group::colored` and `log::colored` failed because the container's TERM=dumb terminal doesn't support 256-color ANSI codes. The snapshots expected \x1b[38;5;10m (256-color green) and \x1b[39m (default fg), but the actual output used \x1b[m (SGR reset).3 minutes
- Install time
- 14 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- Model tokens used
- 220,150
- Exact commit tested
- b3a2077ddc57
- 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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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.
/bin/sh -lc '# Clean up the snapshot/template changes from git tracking cd /work/repo && git diff --stat' in /work/repo succeeded in 0ms: pueue/tests/client/_snapshots/group__colored | 10 +++++----- pueue/tests/client/_templates/log__colored | 4 ++-- 2 files changed, 7 insertions(+), 7 deletions(-) Let me calculate the total elapsed time. I started at approximately 20:06 UTC and it's now 20:20 UT… Here's the final report: tokens used 220,150 Let me calculate the total elapsed time. I started at approximately 20:06 UTC and it's now 20:20 UT… Here's the final report:
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 14 minutes.
- Recovered from all 1 error 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 Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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 | 100.00 | 0.09 | |
| Argusic Runner | 2/3 | Ran out of time | 0.00 | 0.26 |
Topics (from GitHub)
command-linecommand-line-tooldaemonhacktoberfestqueue-managerqueue-tasksrustshell-queue
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/pueue)Questions
- Does pueue run?
- Yes. pueue runs. Argusic installed and launched it on a clean machine in 14 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test pueue?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b3a2077ddc57. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test pueue?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does pueue take to install?
- 14 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 pueue need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing pueue?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for pueue?
- 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.