tmux
tmux source code
Runssource: GitHubCISCcommit a7a3b4b3a806
C, ISC licensed.
tmux runs. An Argusic agent installed it in 8 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
tmux next-3.9 builds from source, starts a server, creates and lists sessions successfully using only locally extracted dependencies.
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. 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.
- Perl scripts had hardcoded /usr paths3 minutes
- Missing autotools (autoconf, automake, bison, m4)2 minutes
- Configure failed with PKG_CHECK_MODULES unexpanded1 minute
- make failed: bison data files not found1 minute
- Install time
- 8 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- ./tmux -V returned 'tmux next-3.9'; TMUX_TMPDIR=/tmp ./tmux -Ltmtest -f/dev/null start-server && new-session -d -s verify && list-sessions returned session listing
- Model tokens used
- 112,065
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
1. Missing autotools (autoconf, automake, aclocal) → downloaded debs from apt cache, extracted to p… 2. Missing `m4` → downloaded `m4` deb, added to prefix 3. Perl scripts had hardcoded `/usr/share/` paths in `@INC` → patched `aclocal-1.16`, `automake-1.1… 4. `autom4te` looked for `/usr/bin/m4` → set `M4` env var 5. Missing `pkg.m4` for PKG_CHECK_MODULES → copied from `/usr/share/aclocal/pkg.m4` into the prefix 6. `bison` couldn't find data files → set `BISON_PKGDATADIR` **Verification:** - `./tmux -V` → `tmux next-3.9` - Server start, session create, list sessions all succeeded with a real tmux instance - Binary size: 8,147,360 bytes ``` ```
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 8 minutes, faster than the median of the 4 comparable projects Argusic has measured.
- 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 ISC, 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.
Of the 5 C projects Argusic has installed and timed, tmux was the 3rd fastest to reach a running state, and 5 of 5 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.
- A quick evaluation: it was running 8 minutes after the clone.
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 8 minutes, hitting 4 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. One attempt is 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.18: 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?
- 8 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?
- 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.
- How does tmux compare with the alternatives?
- Of the 5 C projects Argusic has installed and timed, tmux was the 3rd fastest to reach a running state, and 5 of 5 reached one at all.
- Where is the evidence for tmux?
- 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.