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.