red
:memo: Vimlike Modal Text Editor in Rust
Runssource: GitHubhomepageRustMITcommit 2ed85f3c4db4
Rust, MIT licensed. The project labels itself: ai agent, code editor, coding agent, cross platform, developer tools, git, language server protocol and lsp.
red runs. An Argusic agent installed it in 28 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
red 0.7.0 builds from source with a user-installed Rust 1.99.1 toolchain, all 3662 tests pass, clippy and rustfmt are clean, a fresh profile can run red --check-config successfully, and the interactive TUI launches, edits, saves, and quits on a PTY.
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.
- cargo test --all-targets failed: editor::test::nonrecursive_directory_watch_snapshots_do_not_retain_directory_entries (overlayfs dir size 8192 and mtime can both be unchanged, so non-recursive snapshot missed new file)13 minutes
- red --check-config failed CFG303 on fresh HOME: default log_file cannot open because ~/.config/red not created on utility paths6 minutes
- cargo clippy --all-targets --all-features -- -D warnings failed with 46 pre-existing double_must_use errors at 6 async-trait/async-recursion sites on toolchain 1.99.1 (baseline before my changes also had 48 errors)5 minutes
- no Rust toolchain in container1 minute
- Install time
- 28 minutes
- Cold machine to finish
- 30 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- cargo test --all-targets --all-features -> total passed 3662, failed 0 (26 test binaries); cargo clippy --all-targets --all-features -- -D warnings -> Finished with 0 errors; cargo fmt --check -> OK; ./target/debug/red --version -> 'red 0.7.0'; fresh-HOME ./target/debug/red --check-config -> 'config ok' exit 0; ./target/debug/red --self-check -> 'red self-check ok' exit 0; PTY run of './target/debug/red hello.txt', keystrokes i+EDITED+Esc+':wq' -> process exit 0 and file content 'EDITEDalpha\nbeta\ngamma\n'
- Model tokens used
- 1,016,380
- Exact commit tested
- 2ed85f3c4db4
- 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.
- **Err 1 (0 fix):** No Rust toolchain in the container; `rustup` installed it in ~1 min. - **Err 2:** `red --check-config` failed on a fresh user profile with `CFG303` (default `log_file` … - **Err 3:** `editor::test::nonrecursive_directory_watch_snapshots_do_not_retain_directory_entries`… ## Pre-existing, unfixed - `cargo clippy -D warnings` fails on the untouched tree baseline too (46 `double_must_use` errors … **Verified:** `cargo test --all-targets --all-features` → total passed 3662, failed 0; `cargo clipp… exec /bin/sh -lc 'date -u +"%Y-%m-%dT%H:%M:%SZ"' in /work/repo succeeded in 0ms: 2026-10-29T04:57:00Z tokens used 1,016,380
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 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 MIT, as reported by its host.
What did not, or is not known
- Took 28 minutes to install, slower than the median of the 83 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 84 ai-agent projects Argusic has installed and timed, red was the 77th fastest to reach a running state, and 58 of 84 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)
ai-agentcode-editorcoding-agentcross-platformdeveloper-toolsgitlanguage-server-protocollspmodal-editingneovimopenai-codexrustterminal-editortext-editortree-sittertuivim
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/red)Questions
- Does red run?
- Yes. red runs. Argusic installed and launched it on a clean machine in 28 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test red?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2ed85f3c4db4. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test red?
- The run that produced this verdict cost $0.25: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does red take to install?
- 28 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 red need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing red?
- 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 red compare with the alternatives?
- Of the 84 ai-agent projects Argusic has installed and timed, red was the 77th fastest to reach a running state, and 58 of 84 reached one at all.
- Where is the evidence for red?
- 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.