tmux-ide

The open-source tmux GUI/TUI for your coding agents

Runssource: GitHubhomepageTypeScriptMITcommit 3237d0edc4e1

TypeScript, MIT licensed. The project labels itself: agent orchestration, claude code, codex, coding agent, coding agents, tmux and tmux conf.

tmux-ide runs. An Argusic agent installed it in 37 minutes and hit 5 errors on a clean machine with no GPU, and the whole session was recorded.

tmux-ide in this repo builds and runs real tmux 3.7c sessions with send/ls/adopt/team, a 200-serving command-center REST+SSE API, a working control-socket send verb, and the full managed dev-instance lifecycle;

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 56 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
56 / 100
cost of the verifying run
$0.66 (measured)
recorded runs
2
last tested
stars
569
forks
35
open issues
13
watchers
0
size
102 MB
created
last push

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.

Time lost to each failure while testing tmux-ide, 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.

  • send/ls/adopt/status launched bare 'tmux' (ENOENT) with no system tmux20 minutes
  • No pnpm/Bun/tmux in container; Node 18 below engines (>=20)8 minutes
  • Desktop Vite build fails loading workspace .ts main (ERR_UNKNOWN_FILE_EXTENSION) under Node 224 minutes
  • tmux-ide init crashed (ENOENT templates/default.yml) on the npm dist3 minutes
  • development-container-app tests fail: /usr/bin/ssh missing in container2 minutes
Install time
37 minutes
Cold machine to finish
37 minutes
Errors hit and fixed
5 hit, 3 fixed with no human help
How the result was proved
node bin/cli.js doctor -> 'tmux 3.7c (...)'; tmux-ide send 'Agent 1' 'FINAL_E2E_MESSAGE_42' -> 'Sent to Agent 1 (%13)'; echo confirmed in tmux pipe-pane output; curl /api/sessions,/api/project/ti-demo,/api/project/ti-demo/panes -> 200; pnpm test suites: daemon 6618 pass, contracts 551, daemon-client 273, desktop-renderer 1103, tmux-bridge 70, bun daemon 157, tui renderer 110
Model tokens used
3,166,830
Exact commit tested
3237d0edc4e1
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.

- Installed a working toolchain locally (no root): Node 22.17.1, pnpm 10.21.0 (via corepack), Bun 1…
- `pnpm install --frozen-lockfile` succeeded; `pnpm build:cli` produced `bin/cli.js`.
- Ran the real app end-to-end with no system tmux and no tmux on PATH: `start` created a 4-pane ses…
- The full isolated development-instance lifecycle also works: `dev:instance rebuild` → `up` (daemo…
**Errors found and fixed**
1. **Missing tooling (env)** — no pnpm/Bun/tmux/system dev libs; fixed with user-local Node/pnpm/Bu…
2. **`tmux-ide init` crash** — the npm dist lacks `templates/`, so `init` ENOENT'd on the template;…
3. **Bare-`tmux` spawns broke `send`/`ls`/`adopt`/`team`/`status`/`launch` after an npm install wit…
4. **`/usr/bin/ssh` absent** — 3 pre-existing `development-container-app` tests fail (environment, …
5. **Desktop web build (Vite)** — fails loading a workspace `.ts` main under Node 22 (`ERR_UNKNOWN_…
**Verification numbers**
- Contracts 551 passed (61 files); daemon unit 6618 passed, 3 failed (the `/usr/bin/ssh` env cases)…

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.
  • Ran without a GPU, so it does not need one to start.
  • 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

  • Took 37 minutes to install, slower than the median of the 21 comparable projects Argusic has measured.
  • Hit 5 errors during setup, 2 of which were not solved.

Of the 22 agent-orchestration projects Argusic has installed and timed, tmux-ide was the 19th fastest to reach a running state, and 15 of 22 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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs92.000.66
Argusic Runner1/3Did not run20.000.02

Topics (from GitHub)

agent-orchestrationclaude-codecodexcoding-agentcoding-agentstmuxtmux-conf

Embed the badge

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

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

Questions

Does tmux-ide run?
Yes. tmux-ide runs. Argusic installed and launched it on a clean machine in 37 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test tmux-ide?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3237d0edc4e1. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test tmux-ide?
The run that produced this verdict cost $0.66: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does tmux-ide 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 tmux-ide need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing tmux-ide?
5 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 tmux-ide compare with the alternatives?
Of the 22 agent-orchestration projects Argusic has installed and timed, tmux-ide was the 19th fastest to reach a running state, and 15 of 22 reached one at all.
Where is the evidence for tmux-ide?
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.

Discussion