tmux
tmux source code
Runssource: GitHubCISCcommit a7a3b4b3a806
C, ISC licensed.
tmux runs. An Argusic agent installed it in 18 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
tmux binary builds and runs: version prints as 'tmux next-3.9', sessions can be created and listed, 11 regression tests pass.
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.
- Missing build tools (autoconf, automake, bison, m4) and libraries (libevent-dev, libncurses-dev)5 minutes
- aclocal-1.16 hardcoded /usr/share/aclocal-1.16 and couldn't find Automake perl modules3 minutes
- autom4te failed: autom4te.cfg had hardcoded /usr/share/autoconf paths2 minutes
- bison couldn't find m4 (/usr/bin/m4 hardcoded) or share/bison directory2 minutes
- autoconf and autoheader had hardcoded /usr/share/autoconf paths for trailer.m41 minute
- Install time
- 18 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- `./tmux -V` returned 'tmux next-3.9'; `./tmux new-session -d -s verify && ./tmux list-sessions` listed the session; 7 regression tests (check-names, has-session-return, list-commands, session-ops, environ, buffers, window-ops, new-session-command, pane-ops, server-access, split-window-wait-kill) all exited 0
- Model tokens used
- 200,197
- Exact commit tested
- a7a3b4b3a806
- 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 verdict above comes from a different attempt, so read this as one session and not as the current result. 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.
--- Running split-window-wait-kill.sh --- exit=0 exec /bin/sh -lc '# Verify the final state with key commands cd /work/repo && export LD_LIBRARY_PATH="$PWD/build-prefix/usr/lib/x86_64-linux-gnu" && ./tmux -V 2… succeeded in 362ms: tmux next-3.9 verify: 1 windows (created Sun Nov 1 16:33:23 2026) All done. Here's the final report. tokens used 200,197 All done. 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.
- Recovered from all 5 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 ISC, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 18 minutes to install, slower than the median of the 6 comparable projects Argusic has measured.
Of the 7 C projects Argusic has installed and timed, tmux was the 6th fastest to reach a running state, and 5 of 7 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.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/tmux)Questions
- Does tmux run?
- Yes. tmux runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test tmux?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a7a3b4b3a806. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test tmux?
- The run that produced this verdict cost $0.21: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does tmux take to install?
- 18 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 tmux need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing tmux?
- 5 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.
- How does tmux compare with the alternatives?
- Of the 7 C projects Argusic has installed and timed, tmux was the 6th fastest to reach a running state, and 5 of 7 reached one at all.
- Where is the evidence for tmux?
- 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.