sidex
VS Code rebuilt on Tauri. Same architecture, 96% smaller. Early release.
Runs with mockssource: GitHubhomepageTypeScriptMITcommit ad9786526822
TypeScript, MIT licensed. The project labels itself: code editor, electron alternative, ide, monaco editor, open source, open source project, rust and tauri.
sidex runs, with stand-ins for the services it depends on. An Argusic agent installed it in 45 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
SideX binary launches, stays alive for 10s with all WebKit subprocesses (NetworkProcess, WebProcess, injected bundle) loading successfully from /tmp/sysroot via LD_PRELOAD; frontend builds; npm install succeeds; cargo test reports 205 passed, 2 flaky BM25 failures
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 92 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.
- WebKit subprocess binaries at /tmp/sysroot/ not found at hardcoded /usr/lib path20 minutes
- Rust 1.99 API drift: ssh.rs russh_keys PublicKey::from_bytes removed10 minutes
- Rust 1.99 API drift: tree_sitter_parser.rs &rust_language() missing &5 minutes
- Rust 1.99 API drift: document_color.rs &lsp_info missing &5 minutes
- Rust 1.99 API drift: ssh.rs test clone_public_key().ok()! needs unwrap2 minutes
- Install time
- 45 minutes
- Cold machine to finish
- 34 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- cargo test: 205 passed, 2 flaky BM25 failures; timeout 10 SideX binary stayed alive (exit 124)
- Model tokens used
- 695,274
- Exact commit tested
- ad9786526822
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
tokens used 695,274 Now I have all the data. Here's the full summary. **Setup**: Built the binary with `cargo build` (success), frontend with `npm run build` (success), … **Fixes applied** (accumulated): 1. `crates/sidex-syntax/src/tree_sitter_parser.rs` — added `&` to `&rust_language()` (prior agent) 2. `crates/sidex-lsp/src/document_color.rs` — added `&` to `&lsp_info` (prior agent) 3. `crates/sidex-remote/src/ssh.rs` — replaced `russh_keys::key::ed25519::PublicKey::from_bytes(...… 4. `crates/sidex-remote/src/ssh.rs` — test: `clone_public_key().ok()!` → `clone_public_key().ok().u… 5. `/tmp/webkit_redirect.so` — LD_PRELOAD shim redirecting WebKit subprocess paths from `/usr/lib/.… **Test results** (`cargo test`): 205 passed, 2 flaky BM25 ranking-order failures in `sidex-context`… **Launch**: `SideX` binary starts and stays alive for the full 10s timeout (exit 124 = killed by ti…
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
- Installed in 45 minutes.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 | 1/3 | Runs with mocks | 92.00 | 0.31 |
Topics (from GitHub)
code-editorelectron-alternativeidemonaco-editoropen-sourceopen-source-projectrusttauritypescriptvscode
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/sidex)Questions
- Does sidex run?
- sidex runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 45 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test sidex?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ad9786526822. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test sidex?
- The run that produced this verdict cost $0.31: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does sidex take to install?
- 45 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 sidex need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing sidex?
- 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.
- Where is the evidence for sidex?
- 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.