0.2.1

RepoMagpie 0.2.1

A patch release: RepoMagpie's MCP server is in the MCP Registry, plus two fixes from testing.

• Listed in the MCP Registry as io.github.Varshavia/repomagpie. A client that installs it from there runs npx -y repomagpie@0.2.1 mcp, which serves the read-only tools.
• An alternative your notes say to avoid is now marked: Alternatives: "moment" (your notes say avoid). The mark shows in the hook's line, the recall card, suggest's Instead line, and the app's Check a package and Suggest. Before, the hook named such an alternative with no mark, so it read as a recommendation. A note in your other journal counts too. In the JSON, each alternative has avoid_in.
• Pull first when you turn on shared notes. If your branch tracks a remote branch, the app's Turn on shared notes now says "If a teammate may have turned them on already, pull first." If both machines turned them on, working as a team says how to recover.

Upgrade

npm install -g repomagpie
repomagpie setup

Run setup again so the installed skill matches the CLI. Until you do, repomagpie doctor reports the difference. Your notes need no changes.

Every change is in the changelog.

0.2.0

RepoMagpie 0.2.0

The first stable release. RepoMagpie keeps your notes on the packages and tools you've tried, and your coding agent reads them before it installs anything.

What it does

Months ago you tried pdfkit and gave up on it. Today your agent is about to install it again. With RepoMagpie, the agent sees your note first, and in Claude Code the hook asks you:

$ npm install pdfkit

RepoMagpie: you noted to avoid pdfkit (personal journal)
Verdict: "avoid: async streams painful; use puppeteer"
Alternatives in your personal journal: "puppeteer" (Verdict: "default for PDF rendering")
~/.magpie/notes/npm--pdfkit.md

Do you want to proceed?

• Remember. Write a Verdict in one line: repomagpie note pdfkit "avoid: async streams painful; use puppeteer". At the end of a task, your agent offers once to save a dependency decision, with your reason in your words. Each note is a Markdown file you own, in ~/.magpie/notes/.
• Recall before install. Before an install, your agent calls recall. When a note says to avoid the package, it shows you the note and its alternatives and asks first. A hook checks the install command too, in case the agent skips that step.
• Find by concern. Ask "how should database security work in this project?" or "what do I have for browser testing?", in any language. Your agent finds the notes that fit, by sixteen domains such as security, database and testing, and by tags.
• Suggest and start. repomagpie suggest reads a project's manifests and README and lists your notes that fit it. repomagpie init lists a project's dependencies by what your notes say, and asks for a Verdict on each one without a note.
• Discover. repomagpie discover, or the app's Discover page, searches GitHub by words, domain and kind, says why each result is there, and adds the ones you choose to your inbox.

Install

You need Node.js 22.12 or later, on Linux, Windows or macOS.

npm install -g repomagpie
repomagpie setup
repomagpie doctor

setup shows which files it will change, asks first, and backs up each file it edits. repomagpie setup --dry-run only shows the plan. doctor says what is wired in each agent.

Upgrading from a beta: run npm install -g repomagpie (no @beta), then repomagpie setup again so the installed skill matches the CLI; repomagpie doctor reports the difference until it does. Your notes need no changes.

Seven agents

repomagpie setup sets up the MCP server, the agent skill and, where the agent has one, the install hook:

Agent	When a note says to avoid a package
Claude Code	the hook asks you
Gemini CLI	the hook asks you
Antigravity CLI	the hook asks you
Codex CLI	the hook stops the first try; your agent asks you
Cursor	the hook stops the first try; your agent asks you
Copilot CLI	the hook stops the first try; your agent asks you
VS Code (GitHub Copilot)	no hook; the MCP server and the skill check it

The hook never blocks an install for good and never approves one. Other agents with MCP or Agent Skills can use the server or the skill by hand: see setting up by hand.

Your team's notes

A project journal is a .magpie/ folder in the repository, committed with the code. Every contributor's agent reads it next to their own journal, after git pull.

• Ask your agent to note something "for the team", or run repomagpie note pdfkit "avoid: …" --to project, then commit .magpie/.
• In the app, Turn on shared notes for owner/repo starts the project journal, and Copy to this project copies one of your notes into it.
• The Project view names the repository, for example acme/widget on github.com, and says whether the shared notes are committed and pushed. It reads only your local git.
• When a project note and a personal note on the same package disagree, the project note wins, and your agent mentions yours.

Review rule changes in pull requests, and let leads approve them with a CODEOWNERS line. See working as a team.

The local app

repomagpie ui opens your journals in the browser, on 127.0.0.1 only:

• Inbox review: write the Verdict, pick kind, domains, tags and rating, press Ctrl+Enter.
• Search, Add and Import: Search lists your notes before you type; Import takes a list as people paste it.
• Check a package: what your journals say before an install, and what the hook does in each agent.
• Suggest for this project: the notes that fit, and why each one is a candidate.
• Graph: notes, tags, [[links]] and alternatives, coloured by domain if you choose.

Privacy

• Your journals are Markdown files on your machine. There is no telemetry, no account and no model of RepoMagpie's own: the AI is the coding agent you already use.
• The only network requests are read-only calls to GitHub's API, when you add a note from a GitHub repository or search with Discover. They send that repository's name or your search, and your GitHub token if there is one, never your notes.
• Your agent's model provider sees the notes your agent reads.
• The package has no runtime dependencies. This version is built and staged by the repository's GitHub Actions with npm provenance, then approved by the maintainer.

RepoMagpie comes only from this repository, the npm package repomagpie and the skill on skills.sh. Anything else that calls itself RepoMagpie is not ours.

New since 0.2.0-beta.20

• The app's Project view names the repository, with a link to its page on GitHub, GitLab or Bitbucket, and never shows credentials from the remote's URL. Without a remote, it shows the folder's name and "no remote".
• One line under it says whether the shared notes are committed and pushed.
• "Start this project's journal" is now Turn on shared notes for owner/repo. Afterwards a toast says to commit and push .magpie/, and stays until you dismiss it. repomagpie doctor points to the same action.

Every change since the first beta is in the changelog. To remove RepoMagpie, run repomagpie setup --remove, then npm uninstall -g repomagpie; your journals stay.

0.2.0-beta.20

RepoMagpie 0.2.0-beta.20

The twenty-first pre-release. Teams can share their dependency rules from the first minute: your agent and the app now reach the project journal, .magpie/ in the repository.

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.20. Your notes need no changes. Run repomagpie setup again: the skill changed. It now sends notes "for the team" to the project journal, and it treats a project note as the team's decision.

For teams

• Notes "for the team" reach the project journal. Say "note it for the team" (or "ekip için"), and your agent writes to .magpie/, creating it if needed. When it's unclear which journal you mean, it asks. When a project note and your own disagree, the agent follows the project note and mentions yours.
• Start the project journal from the app. In a git repository, the Project view has Start this project's journal. Then commit .magpie/ to share it.
• Copy a note to the project from the app. Copy to this project (it was "Adopt to project") copies one of your notes. Before the project journal exists, it starts it first. A note in both journals says so in each.
• New guide: Working as a team. It covers starting the journal, reviewing rules in pull requests, a CODEOWNERS line for leads, and what happens when notes disagree.

Easier to use

• A bare package name's type is inferred. repomagpie note moment "…" takes the type of your existing note on moment. With no note and no manifest, it asks, and Enter takes npm. The app's Add starts at npm.
• Plain repomagpie init works. It lists your project's dependencies by what your notes say, then asks for a Verdict on each one without a note. init --auto still works.
• Suggest shows one row per package, with both journals named when both have a note. Packages you noted to avoid appear among the suggestions only when they match what you described. All of them are in a collapsed section at the end.
• The catalog lists project and avoid notes first, so the first page of a big journal holds what matters. A paging cursor from an earlier version starts over from the first page.

Fixed

• repomagpie suggest no longer drops a project note when your personal note on the same package scores much higher.

The full list is in the changelog.

0.2.0-beta.19

RepoMagpie 0.2.0-beta.19

The twentieth pre-release. Search and Import in the app are easier to start with, Discover finds better results and uses your GitHub CLI login, and there are sixteen domains.

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.19. Your notes need no changes. Run repomagpie setup again: the skill now points agents to the frontend domain and says Discover hides lists.

In the app

• Search lists your notes before you type, Verdicts first. When a filter hides what matches, the list says so and offers the fix, for example "No reviewed notes match “pdf”. 2 inbox notes do." with Show inbox notes.
• Import reads lists as you paste them: numbered lines, • bullets, Markdown links and names in backticks. Lines that name nothing are listed with the reason. repomagpie import reads them the same way.
• Each page says what it is for in one line. The details are under How this works.

Discover

• It uses your GitHub CLI login. If you are signed in with gh auth login, you get GitHub's higher limits with nothing to set. The token stays in memory and is never printed or saved. The app and repomagpie doctor say whether RepoMagpie is connected.
• It hides awesome-lists, courses and cheatsheets, and says how many it hid. --include-lists, or Show in the app, brings them back.
• A search with words is sorted by best match. A search without words is still sorted by stars.
• Each result says why it is there, for example "Matched topic: react · matched words: design, system".
• "Hide ones I already have" hides the results you already have a note on.

Sixteen domains

• There are four new domains: mobile, data, docs and payments.
• styling is now frontend, and covers UI frameworks too. Notes and searches that say styling keep working.
• docker now suggests devops.

Fixed

• repomagpie setup --remove --agents <agent> keeps the shared skill in ~/.agents/skills/repomagpie/ while another agent still uses it. If an earlier --remove deleted it, run repomagpie setup again.
• repomagpie doctor's to-do for an untrusted Codex CLI hook now says how to remove it if you don't use Codex CLI.
• A GitHub link to a file, such as .../blob/main/README.md, now makes a note for the repository.

Faster

• Recall and the hook answer sooner right after you change a note. The cache now saves only the changed notes instead of being rewritten whole. On 2,000 notes, recall right after one note changed takes 138 ms instead of 145 ms.

The full list is in the changelog.

0.2.0-beta.18

RepoMagpie 0.2.0-beta.18

The nineteenth pre-release. It has security fixes: please update. They come from the second batch of a security audit of the CLI, the hooks, the MCP server and the app.

Two things work differently after you update:

• The link repomagpie ui prints works once.
• Outside a git repository, a project journal needs --project.

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.18. Your notes need no changes. repomagpie setup updates the skill's version, so repomagpie doctor stops reporting a skill older than the CLI. The skill's text is the same as in beta.17.

Security

• The link repomagpie ui prints works once. The first time you open it, the app opens and your browser gets a cookie. Reloads and new tabs in that browser keep working: open http://127.0.0.1:<port>/, as the CLI now says when it starts. If you open the link again, a page says it was already used. Go to http://127.0.0.1:<port>/ in the browser that has the app open, or start repomagpie ui again for a new link. A copy of the link, for example in the list of running processes, opens nothing once you have used it. The link, the app's cookie and the token for changes are now three different secrets. SECURITY.md says what this protects against and what it doesn't.
• More hidden characters show as markers. Tag characters (U+E0000 to U+E007F) and the supplementary variation selectors (U+E0100 to U+E01EF) in note text now show as markers such as <U+E0041>, like the other hidden characters. This applies in the terminal, in --json, in the hook's messages, in the app, and in notes made from GitHub. Tag characters can spell text you don't see while an agent still reads it. The app's warning about hidden characters covers them too. Emoji keep their variation selector (U+FE0F). Flag emoji built from tag characters, such as England's, now show markers after the black flag.

Changed

• Outside a git repository, a project journal needs --project. Before, RepoMagpie walked up from the current folder and took the first .magpie/ folder it found. Outside a repository, that could be a .magpie/ in a shared folder above yours, such as another user's folder or the drive's root. The hook, recall, search and suggest then read it as your project's notes. Now:

  • Inside a git repository, nothing changes: the repository's .magpie/ is found from any subfolder.
  • Outside one, the hook, recall, search, suggest and catalog read only your personal journal, unless you pass --project <path>.
  • repomagpie note --to project and repomagpie adopt outside a repository fail without --project. Before, they created .magpie/ in the current folder. The message is No project journal here: outside a git repository, use --project <path>.
  • repomagpie doctor's project line says none here; outside a git repository, use --project <path>.

  If you kept a project journal in a folder that isn't a git repository, pass --project <path> to the commands. The hook has no --project, so it reads that journal again only once the folder is a git repository. Decision 0051 has the reasoning.

Docs

• SECURITY.md describes the app's one-time link and its three secrets, and the new hidden characters.
• The spec and the glossary describe how the project journal is found. Decision 0051 replaces the old walk outside a git repository.

The full list is in the changelog.

0.2.0-beta.17

RepoMagpie 0.2.0-beta.17

The eighteenth pre-release. It has security fixes: please update. It also covers Claude Code's Monitor tool in the hook and detects more ways of installing a package.

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.17. Your notes need no changes.

Run repomagpie setup after the upgrade. The Claude Code hook now also runs when Claude Code uses its Monitor tool, which runs shell commands in the background. setup adds Monitor to your existing hook entry. Until you run it, an install that Claude Code starts through Monitor isn't checked, and repomagpie doctor reports the entry without Monitor. setup also updates the skill's version, so doctor stops reporting a skill older than the CLI. The skill's text is the same as in beta.16.

Security

• repomagpie adopt and Adopt in the app no longer print an install command for a package name its registry wouldn't accept. A repository's manifest could name its package so that the printed command ran something else in your shell. Now you get a warning that names the package instead.
• A note from GitHub lists at most 200 of a repository's skills, with a warning when there are more. A repository with thousands of skill folders could grow a note past 256 KB. RepoMagpie doesn't read a note that size, so the hook ignored what you wrote in it. When a note is still over 256 KB, the hook and repomagpie recall --json now say a note couldn't be read, instead of saying nothing.
• On Windows, repomagpie doctor and repomagpie mcp never look at a folder on another machine (\\server\share) that a project's settings or an agent's project argument names. The hooks already worked this way. Looking there could send that machine your Windows sign-in hash.
• RepoMagpie's caches are written to a new file with an unguessable name. A file or link committed to a repository's .magpie/.cache/ can no longer make RepoMagpie write to a file outside the journal.

Fixed

• The hook sees more ways of installing a package: npm's other install names (npm in, npm isntall, npm it, …), pnpm i and pnpm install, bun i and bun install, yarn global add, python -mpip install, a package manager run at a version through npx, bunx, corepack, pnpm dlx or yarn dlx (npx npm@latest install …), and an npm alias, which is now looked up under both names.
• The Claude Code hook also runs on the Monitor tool (see above). repomagpie doctor names an entry without it.
• The hook quotes the path of a project note, as it quotes the note's text, so a file name in a repository's journal can't read as the hook's own words.
• A skill link's name and a repository's description go into a note as one plain line. Hidden characters show as markers, and neither can add a heading to the note.
• repomagpie note --use-when and --avoid-when refuse an item that a code fence left open earlier in the note would hide. Before, they wrote it and said RepoMagpie would ask.
• Add's preview in the app shows hidden characters as markers, such as <U+202E>, with a warning, as the note view does. This covers a note's name, Verdict and other text.
• Refreshing a repository's note from GitHub keeps a package the repository's manifests no longer name when the note has your Verdict or Avoid when, and warns you. Your avoid note still covers that package.

Docs

• SECURITY.md describes how the caches are written and how RepoMagpie treats network paths on Windows.
• The spec documents recall --json's new skipped list, the hook's new install forms and the Monitor matcher. Agents explains why the matcher is Bash|PowerShell|Monitor.

The full list is in the changelog.

0.2.0-beta.16

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 setup

repomagpie --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.

0.2.0-beta.15

RepoMagpie 0.2.0-beta.15

The sixteenth pre-release: new notes from GitHub get a better kind.

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.15. Your notes need no changes.

Run repomagpie setup after the upgrade. The skill's text is the same as in beta.14, but its version changed, and until you run setup, repomagpie doctor reports a skill older than the CLI.

Changed

• A better kind for a new note from GitHub. RepoMagpie drafts the kind (library, framework, cli, skill-pack, …) when you note a repository. Now:

  • a GitHub Action (a root action.yml) is other;
  • a library or framework that ships agent skills for its users, such as playwright or prisma, is no longer a skill pack;
  • the topics orm, ui-library and testing-framework name the kind;
  • so do a few phrases at the start of the README, such as "a framework for", "component library" or "development platform".

  On 69 public repositories the kind is right for 37 instead of 24. On 30 others, labelled before any rule changed and checked only at the end, it is right for 15 instead of 14. The kind is still a draft you can change, and notes you already have don't change.

• Discover's estimated kind reads the same topics, so repomagpie discover --kind library also keeps repositories tagged orm or ui-library.

Fixed

• Removing a suggested domain with the keyboard. In the app, after the × removes a suggested domain, the focus moves to the next suggestion again. On a slow machine, the focus could be lost instead, so the next Enter did nothing. The bug came in 0.2.0-beta.14.

Docs

• Decision 0047: each kind's deciding question, the held-out set and the new rules, measured one at a time. The note schema lists the deciding questions.
• Decision 0048: the local app's first files. The pages and dialogs the first screen doesn't show now load in one chunk after the first rows are on screen. The size limit for what every screen loads first is 104.0 kB gzipped, with no allowance.
• For contributors: npm run measure reports every number an optimisation is judged by, npm run build:analyze shows what the app's scripts are made of, and npm run release:tag tags only a merged release.

The full list is in the changelog.

Known limits

• The kind is right for about half of the 69 repositories in the eval, and for half of the 30 held out. Repositories without telling topics or README phrases still often come out other; reading the manifests' command entries is a candidate next step.
• In the app, a page you open in the first moment after the app opens can show "Loading…" briefly. If the app was upgraded while its tab stayed open, a page can say it couldn't load; Reload fixes it.
• 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.

0.2.0-beta.14

RepoMagpie 0.2.0-beta.14

The fifteenth pre-release: Discover. Search GitHub from the CLI or the app by words, concern and kind, see which repositories you already have a note on, and add the ones you choose to your inbox. New notes from GitHub get a better kind and better suggested domains, and a wrong suggested domain goes in one click, with Undo.

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.14. Your notes need no changes.

Run repomagpie setup after the upgrade, so your agents get the new skill. It has one new paragraph: for "find me a … library", the agent runs repomagpie discover --json, shows a few results and adds one only when you pick it. Until you run setup, repomagpie doctor reports a skill older than the CLI.

Set GITHUB_TOKEN if you search often. Without a token, GitHub allows 10 searches a minute, counted for your public IP address and shared with everything else that uses it. A token gives you 30 of your own. export GITHUB_TOKEN=$(gh auth token) (in PowerShell, $env:GITHUB_TOKEN = gh auth token).

Added

• Discover in the CLI. Search GitHub's repositories and see, for each one, its stars, forks, last push, licence, an estimated kind and domains, and whether a journal already has a note on it, with your Verdict, or "What it does" when it has no Verdict.

  repomagpie discover "pdf invoice" --domain api --language TypeScript
  repomagpie discover --domain styling --kind library --min-stars 1000
  repomagpie note https://github.com/<owner>/<repo>

  • Filters: --domain, --kind, --topic, --language, --min-stars (10 by default), --updated-within (2 years by default), --include-archived, --sort, --limit, --page. --json for your agent.
  • A domain searches its 3 most common GitHub topics, one request each, since GitHub's search can't combine topics with OR. Without a token it searches 2 and names the one left out.
  • A kind that only a repository's files can tell, such as library or cli, is chosen from the estimates, so that filter is approximate and says so.
  • Rate limits: a limit that ends within a minute is waited out once, and the CLI says so. If GitHub stops a search partway, you get the results it found, with a warning. A wait is said in seconds, or as a time that hasn't passed yet.
  • The same search within 10 minutes is answered from a cache in your personal journal, and says so.
  • REPOMAGPIE_DEBUG_HTTP=1 prints each GitHub request's status and rate-limit headers on stderr, never a token, if you need to see why GitHub limits a search.

• Discover in the app. repomagpie ui has a Discover page under Add: the same search with filters, result cards, "Add to inbox", "Add with a Verdict…", and several at once with "Add N to inbox", which says what was added, what was there already and what failed. Without a token it asks before adding more than 5.

• Remove a suggested domain in the app. The × beside a suggested domain's check takes that suggestion out of the note and changes nothing else. The toast offers Undo for 10 seconds, which puts it back where it was. repomagpie domains --suggest doesn't bring a removed suggestion back.

Changed

• Better kind and domains for a new note from GitHub. RepoMagpie now also reads the start of the README, the keywords in package.json, pyproject.toml or Cargo.toml, and whether the repository is a GitHub Action. On 69 public repositories, the kind is right for 24 instead of 21, and 51 of 60 expected domains are suggested instead of 49, with no more wrong ones. A profiling topic no longer suggests performance. A README without a description also gives the "What it does" draft. Notes you already have don't change.

Privacy

Discover is a new network request: GET https://api.github.com/search/repositories, with your search words and filters, and GITHUB_TOKEN when it is set. It runs only when you search. Nothing from your journals is sent. In the app, the local server makes the request, never the browser. The MCP server stays offline: it has no Discover tool. SECURITY.md lists it.

Docs

• Decision 0045 (Discover: where it runs, the requests, the cache, rate limits) and 0046 (the README, manifest keywords and the Action file as classification signals, with the eval's numbers).
• npm run eval:classification: the kind and domains of 69 public repositories, expectations written by hand before the code ran.

The full list is in the changelog.

Known limits

• Without a token, a domain search leaves out its third topic, and other programs or devices on your network can use up the 10 searches a minute before RepoMagpie sends one.
• Discover sees what GitHub's search sees: names, descriptions and topics, not READMEs. Its estimated kind can differ from what repomagpie note decides once it reads the repository.
• The kind is still right for only about a third of the 69 repositories in the eval; it's a candidate follow-up.
• 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.

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.