ttt
TTT Editor (Terminal Text Tool): A real alternative to VS Code, Zed, and Sublime that runs in your terminal. A TUI that feels like GUI. Single binary, zero config.
Runssource: GitHubhomepageGoMITcommit 63f10d525283
Go, MIT licensed. The project labels itself: cli, code editor, developer tools, diff, editor, git integration, go and golang.
ttt runs. An Argusic agent installed it in 11 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
ttt builds from source, all 31 Go packages pass tests, all 100 functional test files pass (370 tests), all 7 integration test files pass (39 tests), and the binary launches via --exec harness rendering the Explore panel
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.
- Go not installed (missing go binary)2 minutes
- Node.js v18 too old for vitest v4 (needs node >=20)2 minutes
- rolldown native binding @rolldown/binding-linux-x64-gnu missing1 minute
- git user.name/user.email not configured, causing git operations in tests to fail1 minute
- Some functional/integration tests timed out at default 15-30s in container
- Install time
- 11 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- go test ./... exited 0 (31 packages); npx pnpm vitest run on all 100 functional test files passed (370 tests, 22 expected fail); npx pnpm vitest run on all 7 integration test files passed (39 tests); bin/ttt --version printed 'ttt dev'; bin/ttt --exec 'wait-for Explore; quit' exited 0 and rendered the Explore pane correctly
- Model tokens used
- 168,673
- Exact commit tested
- 63f10d525283
- 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.
- **Functional tests** (100 files, 370 tests): all pass (22 expected failures) - **Integration tests** (7 files, 39 tests): all pass (LSP tests skipped, expected) - **Binary**: `bin/ttt dev` — launches and renders via `--exec` harness tokens used 168,673 All verified. Here's the final result: ## Summary The ttt Terminal Text Tool is fully operational in this container. After resolving five issues (mis… - **Go tests** (31 packages): all pass - **Functional tests** (100 files, 370 tests): all pass (22 expected failures) - **Integration tests** (7 files, 39 tests): all pass (LSP tests skipped, expected) - **Binary**: `bin/ttt dev` — launches and renders via `--exec` harness
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 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 11 minutes to install, slower than the median of the 127 comparable projects Argusic has measured.
Of the 128 cli projects Argusic has installed and timed, ttt was the 107th fastest to reach a running state, and 117 of 128 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
Topics (from GitHub)
clicode-editordeveloper-toolsdiffeditorgit-integrationgogolangherdr-pluginidelspsyntax-highlightingtcellterminalterminal-emulatortexttext-editorttttuivscode-alternative
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ttt)Questions
- Does ttt run?
- Yes. ttt runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test ttt?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 63f10d525283. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test ttt?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ttt take to install?
- 11 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 ttt need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ttt?
- 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 ttt compare with the alternatives?
- Of the 128 cli projects Argusic has installed and timed, ttt was the 107th fastest to reach a running state, and 117 of 128 reached one at all.
- Where is the evidence for ttt?
- 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.