Repository navigation
0.2.0-beta.16
Pre-release
Pre-release
RepoMagpie 0.2.0-beta.16
The seventeenth pre-release: the graph opens faster, the hook and recall answer faster right after you change a note, and the README is shorter, with screenshots of today's app.
Install or upgrade
You need Node.js 22.12 or later.
npm install -g repomagpie@beta
repomagpie --version
repomagpie setuprepomagpie --version prints 0.2.0-beta.16. Your notes need no changes.
Run repomagpie setup after the upgrade. The skill's text is the same as in beta.15, but its version changed, and until you run setup, repomagpie doctor reports a skill older than the CLI.
The first repomagpie recall, or the first install the hook checks, after the upgrade rebuilds recall's cache once (recall-index.json), so it takes about as long as a cold start. After that it is fast again.
Changed
- The graph opens faster. The layout stops when the nodes settle, instead of always running 300 rounds, and each note is parsed once for the note list, the links and the graph. With 2,000 notes, the first frame of a cold open went from 1,892 to 949 ms on the maintainer's Windows machine.
- Reopening the graph is almost instant when nothing changed. In the same session, the graph is drawn where it was when you left it, with no layout: at 2,000 notes, 1,326 → 241 ms. A new note starts next to a neighbour, and nothing drawn before moves. "Re-run layout" still lays everything out from the start. A reload of the page starts from scratch, as before.
- The hook and recall answer faster right after you change a note. Recall's cache now keeps one entry per note file, so a change re-reads that note instead of every note. With 2,000 notes, recall right after one note changed went from 673 to 144 ms, and the hook from 664 to 135 ms.
Docs
- A shorter README (2,500 → 1,884 words), with Quick start in three steps. The details it dropped moved into
docs/, and the screenshots are retaken from today's app. - Decision 0049: the graph's layout stop rule, positions for the session, and one parse per note. Keeping positions across reloads was weighed and left for later.
- Decision 0050: recall's cache per note file. Node's compile cache and loading the MCP tools lazily were tried and dropped: neither met its bar.
- Agents explains the hook's start-up time on Windows.
The full list is in the changelog.