xedit
Local-first like Obsidian, polished like Notion. Free & open source: wiki links, slash commands, to-dos, local or cloud sync, and MCP for AI. Web + Mac.
Runssource: GitHubhomepageTypeScriptMITcommit 1f745aaedf5f
TypeScript, MIT licensed. The project labels itself: editor, local first, markdown, markdown editor, mcp, model context protocol, nextjs and note taking.
xedit runs. An Argusic agent installed it in 8 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
xEdit builds and runs: the Next.js standalone server answers HTTP 200 on / and /api/config, the 480-test suite passes, and a real registration plus credentials login round-trip against a local PostgreSQL database returns a session and the user's welcome document.
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.
- No system PostgreSQL or Docker available3 minutes
- Container Node v18.19.1 too old for Next.js 16 (needs >=20.9; EBADENGINE warnings)2 minutes
- Embedded Postgres tar has no psql/createdb1 minute
- next start fails with output: standalone (Next.js 16 breaking change)1 minute
- EADDRINUSE addr already in use :3000 and HTTP 000 from stray background server processes1 minute
- Install time
- 8 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- npm test exited 0 (53 files, 480 passed); npm run build exited 0 (BUILD_ID viEPVZsR6iT0xstEgNIks); npm run lint exited 0; curl localhost:3000/ returned 200; curl /api/config returned 200; POST /api/register returned 200 {ok:true}; auth callback returned 302; session returned [email protected]; GET /api/documents returned welcome doc
- Model tokens used
- 149,833
- Exact commit tested
- 1f745aaedf5f
- 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.
- `npm install` → 733 packages added, Prisma client generated (passed).
- `npm run build` → Next.js 16.2.10, standalone output, BUILD_ID generated (passed).
- `npm run lint` → eslint exited 0 (passed).
- `npm test` → 53 test files, 480 tests passed (exited 0).
- Server launched via `node .next/standalone/server.js`; `GET /` → HTTP 200, `GET /api/config` → HT…
- Real end-to-end: `POST /api/register` → HTTP 200 `{"ok":true}`; user verified in PostgreSQL; cred…
Errors fixed (5):
1. Container Node was v18.19.1, too old for Next.js 16 (needs ≥20.9) — EBADENGINE warnings. Fixed b…
2. No system PostgreSQL and no Docker. Fixed by downloading embedded PostgreSQL 16.4 binaries (`zon…
3. Embedded package had no `psql`/`createdb`. Fixed by using `pg8000` (installed in a python venv) …
4. `next start` does not work with `output: "standalone"` — a Next.js 16 breaking change (AGENTS.md…
5. Initial launch confusion: stray background processes caused `EADDRINUSE: address already in use …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 8 minutes.
- Recovered from all 5 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
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 8 editor projects Argusic has installed and timed, xedit was the 4th fastest to reach a running state, and 7 of 8 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.
- A quick evaluation: it was running 8 minutes after the clone.
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)
editorlocal-firstmarkdownmarkdown-editormcpmodel-context-protocolnextjsnote-takingnotion-alternativeobsidian-alternativereactself-hostedtypescriptwriting
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/xedit)Questions
- Does xedit run?
- Yes. xedit runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test xedit?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1f745aaedf5f. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test xedit?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does xedit take to install?
- 8 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 xedit need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing xedit?
- 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.
- How does xedit compare with the alternatives?
- Of the 8 editor projects Argusic has installed and timed, xedit was the 4th fastest to reach a running state, and 7 of 8 reached one at all.
- Where is the evidence for xedit?
- 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.