0.2.0-beta.13

RepoMagpie 0.2.0-beta.13

The fourteenth pre-release: domain suggestions now follow what a package is for. Browser automation and scraping tools aren't "testing", a Docker image doesn't make a project "devops", and a bare "ai" topic no longer comes first.

Install or upgrade

You need Node.js 22.12 or later.

npm install -g repomagpie@beta
repomagpie --version
repomagpie setup

repomagpie --version prints 0.2.0-beta.13. Your notes need no changes. The skill's text is the same as in beta.12, but its version follows the CLI's: run repomagpie setup so repomagpie doctor doesn't report a skill older than the CLI.

Fixed

• Suggested domains fit what a package is for. These are the domains RepoMagpie suggests from a note's GitHub topics and tags, when you save a note or run repomagpie domains --suggest.
  • A browser automation or scraping tool no longer gets testing from its playwright topic. browser-use and crawl4ai now get ai; maxun gets api. Playwright itself still gets testing.
  • A project that ships a Docker image no longer gets devops from docker. Topics that name the concern still do: kubernetes, ci, deployment, infrastructure.
  • The domain named by most of a note's topics and tags comes first. supabase gets database, auth, then ai, instead of ai first.
  • A bare ai topic counts only when the note names nothing else.
  • Design topics (design, ui-design, web-design, frontend-design, ui-ux) now suggest styling.

If you ran repomagpie domains --suggest on beta.12

Your notes keep the suggestions they got then: domains --suggest only fills notes that have no domains yet, and it never changes a suggestion. Suggested domains are outlined in repomagpie ui and count half in search, so a wrong one costs little, but you can remove it:

• In the app, open the note, click the wrong domain's check button to confirm it, then click Edit, unpick that domain under Domains and click Save. The app can't yet remove a suggested domain in one step.
• In the file, delete the value from the note's domains_suggested list.
• To get this release's suggestions instead, delete the domains_suggested line from a note that has no confirmed domains, then run repomagpie domains --suggest --dry-run and repomagpie domains --suggest again.

The full list is in the changelog.

Known limits

• Scraping and browser automation have no domain: none of the 12 is that concern. Such notes are found by their tags and words.
• The retrieval numbers come from synthetic fixtures, and how well agents map questions onto domains isn't measured yet (evals/skill/ is ready but not run).
• The graph's cold first open on 2,000 notes takes about 2 s, sometimes a little over its 2 s target. A warm open is within it.
• The Stop reminder is for Claude Code only. It reminds the agent; it doesn't make it offer.
• Nothing empties the trash. Delete a file in .trash/ to remove it for good, or move it back to notes/ without its stamp to restore it.
• On Windows, Codex CLI, Copilot CLI, Gemini CLI and Cursor start every hook through Windows PowerShell, which adds about 255 ms to each shell command.
• In Codex CLI, Cursor and Copilot CLI, an agent that retries on its own without asking you gets through on the second try. The hook tells it not to, and you see a line saying what happened.
• An entry names one Node.js and one install. After switching Node.js versions, run repomagpie doctor, then repomagpie setup again.