Yes. tmuxp runs. Argusic installed and launched it on a clean machine in 22 minutes, hitting 8 errors on the way, and recorded the session.

How did Argusic test tmuxp?

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

What did it cost to test tmuxp?

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

How long does tmuxp take to install?

22 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 tmuxp need a GPU?

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

What goes wrong when installing tmuxp?

8 things broke in the recorded run, and 8 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for tmuxp?

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.

tmuxp

🖥️ Session manager for tmux, built on libtmux.

Runssource: GitHub homepagePythonMITcommit 315337131105

Python, MIT licensed. The project labels itself: cli, cli utilities, json, python, session manager, teamocil, terminal and tmux.

tmuxp runs. An Argusic agent installed it in 22 minutes and hit 8 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

tmuxp 1.74.0 is installed in a Python venv at ~/venv, tmux 3.4 extracted from Debian packages runs via LD_LIBRARY_PATH and PATH, all 770 tests pass (2 skipped: suppress_history test and AI-generated skip), tmuxp load creates sessions from YAML workspaces, tmuxp freeze snapshots them, and debug-info reports all versions 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

verdict: Runs
Argusic Score: 100 / 100
cost of the verifying run: $0.05 (measured)
recorded runs: 1
last tested: 2026-10-02
stars: 4,588
forks: 247
open issues: 138
watchers: 48
size: 13 MB
created: 2013-08-27
last push: 2026-09-28

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

tmux binary not installed5 minutes
libutempter.so.0 missing for extracted tmux binary2 minutes
libevent_core-2.1.so.7 missing for extracted tmux binary2 minutes
pip install failed due to externally-managed-environment2 minutes
tests/test_docs_tmux_layout.py ImportError: No module named docutils/sphinx2 minutes
test_search_no_args_shows_help - tmuxp not on PATH for subprocess calls1 minute

Install time: 22 minutes
Cold machine to finish: 11 minutes
Errors hit and fixed: 8 hit, 8 fixed with no human help
How the result was proved: pytest tests/ exited 0, 770 passed, 2 skipped; tmuxp --version returned tmuxp 1.74.0, libtmux 0.61.0; tmuxp load -d test_session.yaml loaded a session successfully; tmuxp freeze test-load -y froze the session to YAML; tmux -V returned tmux 3.4
Model tokens used: 78,420
Exact commit tested: 315337131105
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.

....................................................                     [100%]
770 passed, 2 skipped in 20.82s
I have all the information. Let me compile the complete report.
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 22, "errors": [{"msg": "py…
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT:{\"install_succeeded\": true, \"launch_succeeded\": true, \"insta…
 succeeded in 0ms:
tokens used
78,420

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 8 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 MIT, as reported by its host.

What did not, or is not known

Took 22 minutes to install, slower than the median of the 41 comparable projects Argusic has measured.
Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 42 cli projects Argusic has installed and timed, tmuxp was the 41st fastest to reach a running state, and 38 of 42 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.

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.05	2026-10-02 10:26 UTC

Topics (from GitHub)

cli cli-utilities json python session-manager teamocil terminal tmux tmuxinator yaml

Embed the badge

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

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

Questions

Does tmuxp run?: Yes. tmuxp runs. Argusic installed and launched it on a clean machine in 22 minutes, hitting 8 errors on the way, and recorded the session.
How did Argusic test tmuxp?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 315337131105. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test tmuxp?: The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does tmuxp take to install?: 22 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 tmuxp need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing tmuxp?: 8 things broke in the recorded run, and 8 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does tmuxp compare with the alternatives?: Of the 42 cli projects Argusic has installed and timed, tmuxp was the 41st fastest to reach a running state, and 38 of 42 reached one at all.
Where is the evidence for tmuxp?: 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.