tuios
A terminal window manager that knows what your agents are doing. Tiling panes, workspaces, sessions that survive restarts, and one Inbox for every coding agent.
Runssource: GitHubhomepageGoMITcommit 94dbf2bd82b3
Go, MIT licensed. The project labels itself: ai agents, bubbletea, charm, claude code, cli, codex, coding agents and developer tools.
tuios runs. An Argusic agent installed it in 16 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
tuios and tuios-web binaries build from source, the full Go test suite (49 packages) passes, and the daemon creates sessions, accepts typed input via send-text/send-keys, and captures pane output showing shell command execution.
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.
- Install time
- 16 minutes
- Cold machine to finish
- 22 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- go test ./... exited 0 with 49 packages all ok; then daemon started, 'tuios new --detach' created session, 'tuios list-sessions' showed it, 'tuios send-text' and 'tuios send-keys Enter' sent 'echo hello from tuios' into a window, and 'tuios capture-pane' returned the shell prompt and the echoed output confirming execution
- Model tokens used
- 108,391
- Exact commit tested
- 94dbf2bd82b3
- 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.
=== tuios-web version === tuios-web version dev Commit: none Built: unknown By: unknown === Binary sizes === -rwxrwxr-x 1 runner runner 36M Sep 30 10:23 tuios -rwxrwxr-x 1 runner runner 46M Sep 30 10:24 tuios-web All results are in. Here's the summary: tokens used 108,391 All results are in. Here's the summary:
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.
- Nothing broke on the way: zero errors between clone and running.
- 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 16 minutes to install, slower than the median of the 31 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 32 ai-agents projects Argusic has installed and timed, tuios was the 25th fastest to reach a running state, and 22 of 32 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.
- Following its own README: the documented path worked with nothing to fix.
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
Topics (from GitHub)
ai-agentsbubbleteacharmclaude-codeclicodexcoding-agentsdeveloper-toolsgogolangmultiplexerptysshterminalterminal-emulatorterminal-multiplexertiling-window-managertmux-alternativetuiwindow-manager
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/tuios)Questions
- Does tuios run?
- Yes. tuios runs. Argusic installed and launched it on a clean machine in 16 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test tuios?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 94dbf2bd82b3. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test tuios?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does tuios take to install?
- 16 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 tuios need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing tuios?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does tuios compare with the alternatives?
- Of the 32 ai-agents projects Argusic has installed and timed, tuios was the 25th fastest to reach a running state, and 22 of 32 reached one at all.
- Where is the evidence for tuios?
- 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.