Ferrite
A fast, lightweight text editor for Markdown, JSON, YAML, and TOML files. Built with Rust and egui for a native, responsive experience.
Runssource: GitHubRustMITcommit 3ba085c56167
Rust, MIT licensed. The project labels itself: cross platform, editor, egui, json, markdown, markdown editor, mermaid and native app.
Ferrite runs. An Argusic agent installed it in 12.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Ferrite 0.3.0 builds and runs on Linux x86_64 with RUST_FONTCONFIG_DLOPEN=1, 1597/1602 tests pass, binary responds to --help and --version correctly
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.
- 42 test compilation errors: missing TextBuffer import, flowchart module private, missing CHECK/X imports, missing expand_rect import, missing to_markdown method, float precision issue15 minutes
- fontconfig.pc not found - libfontconfig1-dev not installed (no root)1 minute
- Install time
- 13 minutes
- Cold machine to finish
- 40 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- cargo test exited 0 with 1597 passed, 3 failed, 2 ignored
- Model tokens used
- 939,585
- Exact commit tested
- 3ba085c56167
- 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.
**Summary of what I did:** 1. **Installed Rust** (1.92.0) via rustup since it wasn't present 2. **Set up build env**: Created `.pc` files for `fontconfig` (missing dev packages since no root),… 3. **The binary compiled cleanly** on the first try 4. **Fixed test compilation errors** (42 errors → 0): - `history.rs`: Added missing `TextBuffer` import with `#[cfg(test)]` - `code_execution.rs`: Added `CHECK`/`X` import with `#[cfg(test)]` - `edges.rs`: Added `expand_rect` import in test module - `mermaid/mod.rs`: Made `flowchart` module `pub(crate)`, fixed test imports to use `parser::` s… - `productivity_panel.rs`: Added `to_markdown()` method to `Task` 5. **Test results**: 1597 passed, 3 failed (all pre-existing bugs unrelated to my changes), 2 ignor… 6. **Binary verified**: `cargo run -- --help` and `--version` both work (ferrite 0.3.0)
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 12.5 minutes, faster than the median of the 12 comparable projects Argusic has measured.
- Recovered from all 2 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.
Of the 13 cross-platform projects Argusic has installed and timed, Ferrite was the 6th fastest to reach a running state, and 10 of 13 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)
cross-platformeditoreguijsonmarkdownmarkdown-editormermaidnative-appproductivityrusttext-editorwysiwygyaml
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ferrite)Questions
- Does Ferrite run?
- Yes. Ferrite runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test Ferrite?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3ba085c56167. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Ferrite?
- The run that produced this verdict cost $0.40: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Ferrite take to install?
- 12.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 Ferrite need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Ferrite?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Ferrite compare with the alternatives?
- Of the 13 cross-platform projects Argusic has installed and timed, Ferrite was the 6th fastest to reach a running state, and 10 of 13 reached one at all.
- Where is the evidence for Ferrite?
- 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.