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.