lapce
Lightning-fast and Powerful Code Editor written in Rust
Runssource: GitHubhomepageRustApache-2.0commit b604d57de4a8
Rust, Apache-2.0 licensed. The project labels itself: code editor, developer tools, rust, text editor and vim.
lapce runs. An Argusic agent installed it in 17 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Lapce builds from source, passes all 13 unit tests with 0 failures, responds to --help and --version, and launches as a GUI window on the virtual display that stays running despite Vulkan/EGL warnings about missing GPU drivers.
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.
- Rust toolchain not installed (rustc: not found)0.5 minutes
- Cannot install system dev packages via apt (no root, lock denied)0.5 minutes
- Vulkan: no GPU drivers found in container (vkCreateInstance: Found no drivers)
- Install time
- 17 minutes
- Cold machine to finish
- 21 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- cargo test --workspace exited 0 (13 passed, 1 ignored); lapce --version printed 'Lapce 0.4.6+Debug.b604d57'; lapce --new --wait launched on DISPLAY=:99 and remained alive for >5s (kill -0 succeeded); lapce-proxy --help printed usage and exited 0
- Model tokens used
- 420,414
- Exact commit tested
- b604d57de4a8
- 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.
tokens used 420,414 Now I have all the data I need. Let me compile the final result. **Summary of what was done:** 1. **Rust toolchain installed** – `rustup.rs` (rustc 1.98.1, cargo 1.98.1) 2. **No-root constraint** – Apt install of dev packages blocked, but the required headers were pre-… 3. **`cargo build`** – debug build completed in ~5m06s, producing `lapce` (1.2G) and `lapce-proxy` … 4. **`cargo test --workspace`** – all 13 unit tests passed, 1 doc-test ignored, 0 failed. 5. **`lapce --help`** – printed usage, exit 0. 6. **`lapce --version`** – printed `Lapce 0.4.6+Debug.b604d57`, exit 0. 7. **`lapce --new --wait`** – launched on Xvfb `:99`, stayed running for 5+ seconds (confirmed by `… 8. **`lapce-proxy --help`** – printed usage, exit 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 17 minutes.
- Recovered from all 3 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 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.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.07 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.12 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/lapce)Questions
- Does lapce run?
- Yes. lapce runs. Argusic installed and launched it on a clean machine in 17 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test lapce?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b604d57de4a8. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test lapce?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does lapce take to install?
- 17 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 lapce need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing lapce?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for lapce?
- 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.