kibi

A text editor in ≤1024 lines of code, written in Rust

Runssource: GitHubRustApache-2.0commit 6c386fd91ed4

Rust, Apache-2.0 licensed. The project labels itself: 1024, console, editor, editors, rust, syntax highlighting, terminal and text editor.

kibi runs. An Argusic agent installed it in 2.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

kibi builds from source on Linux x86_64 with Rust 1.100.0; all 98 tests pass; the binary prints its version and correctly rejects invalid options and missing TTY.

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.02 (measured)
recorded runs
2
last tested
stars
1,963
forks
119
open issues
32
watchers
6
size
3 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.

Install time
3 minutes
Cold machine to finish
2 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
cargo test exited 0, 76 unit + 22 integration = 98 passed; cargo run -- --version returned 'kibi 0.3.3'; cargo run -- --invalid returned error 1 with expected message; cargo build --release succeeded
Model tokens used
34,759
Exact commit tested
6c386fd91ed4
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.

running 0 tests
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
exec
/bin/sh -lc 'cd /work/repo && . "$HOME/.cargo/env" && cargo test 2>&1 | grep -E "''^test result" | …
 succeeded in 0ms:
test result: ok. 76 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
test result: ok. 22 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s
Everything is clean. Now generating the final answer.
tokens used
34,759
Everything is clean. Now generating the final answer.

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.
  • Installed in 2.5 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 2.5 minutes after the clone.
  • 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.02
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

1024consoleeditoreditorsrustsyntax-highlightingterminaltext-editortuiutf-8

Embed the badge

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

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

Questions

Does kibi run?
Yes. kibi runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test kibi?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6c386fd91ed4. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test kibi?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does kibi take to install?
2.5 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 kibi need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing kibi?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for kibi?
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