Repomagpie

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

$ 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 your verdict, in your own words, on every repo and tool you try: when to use it, when to avoid it, and what to use instead. repomagpie note pdfkit "avoid: async streams painful; use puppeteer" writes one, and your agent offers, once at a task's end, to save a decision with your reason. Each note is a Markdown file you own.
• Recall: your agent checks those verdicts before it picks a tool, through the skill and the MCP server. Ask "what do I have for browser testing?" in any language, or let repomagpie suggest list the notes that fit a project. If your agent tries to install something you ruled out, the hook stops it so that you're asked first.
• Discover: find new repos on GitHub by words, concern and kind, and add them to your journal with your take: repomagpie discover, or the app. Each result says why it is there.

It works in seven coding agents, among them Claude Code, Codex CLI, Cursor and Gemini CLI. Everything stays local: plain Markdown files on your machine, no account, no cloud server. For teams, the same notes can live in the repository and be shared through git (below).

Status: stable and in active development. The changelog lists every version; the roadmap shows what comes next.

Quick start

1. Install the repomagpie command and set it up in your coding agents:

   bash

   npm install -g repomagpierepomagpie setup

   setup shows which files it will change, asks first, and backs up each file it edits; repomagpie setup --dry-run only shows the plan (agents).

2. Check what is wired in each agent:

   bash

   repomagpie doctor

   doctor also lists setup's backups, which can hold your agents' secrets (SECURITY.md); repomagpie setup --delete-backups deletes them.

3. Write your first note. A GitHub URL also fetches the repository's licence, topics and agent skills, and --use-when lets you find the note later by what you need:

   bash

   repomagpie note pdfkit "avoid: async streams painful; use puppeteer" --type npm --alternative puppeteerrepomagpie note https://github.com/microsoft/playwright-cli "use for agent browser tests" --use-when "an agent checks a web UI"

   GitHub allows 60 requests an hour without a token. To raise the limit, sign in with the GitHub CLI (gh auth login): RepoMagpie uses its login. Or set GITHUB_TOKEN or GH_TOKEN. repomagpie doctor says which one it uses.

[!IMPORTANT] RepoMagpie comes only from this repository, the npm package repomagpie and the agent skill on skills.sh. There are no installers, no .exe or other downloads, no other packages and no other website: anything else that calls itself RepoMagpie is not ours (SECURITY.md).

How it works

[How RepoMagpie works: your agent is about to run npm install pdfkit; the skill or the MCP tool recall checks first, and the hook checks the install command as a backstop; both read your personal journal in ~/.magpie and the project journal in .magpie/; your Verdict, "avoid: async streams painful; use puppeteer", comes back, and your agent asks you before the install.]

Before your agent picks a tool, the skill tells it to check your journals: search or suggest while it chooses, and recall before an install, as MCP tools or repomagpie commands. Your verdicts come back first. What worked for you is suggested; when a note says to avoid a package, your agent shows it to you and asks first. The hook checks the install command itself, in case the agent skips that step.

There is no extra model, no API key and no telemetry. RepoMagpie works as well as your agent follows the skill; without a hook, that includes the check before an install.

Ask your agent

• What do I have for browser testing? Your agent searches your journals and answers with the notes it finds, Verdict first.
• How should database security work in this project? Your agent answers with your notes in the security and database domains that fit the project, and says why.
• Install pdfkit. Your agent recalls it first, shows your avoid note with its alternatives, and asks you before it installs anything.
• Which of my tools fit this project? suggest reads the project's manifests and README; your agent picks the notes that fit and names any dependency in use that you noted to avoid.

What each agent gets

What repomagpie setup sets up in each agent, on Linux, Windows or macOS with Node.js 22.12 or later (agents):

Codex CLI runs a new hook only after you trust it in /hooks. Other agents with MCP or Agent Skills can use the server or the skill: see setting up by hand. The package has no runtime dependencies, and paths with letters outside ASCII work.

Share notes with your team

A project journal is a .magpie/ folder in the repository, committed with the code. RepoMagpie's hook and recall read it for every contributor, next to each person's own journal.

repomagpie note pdfkit "avoid: async streams painful; use puppeteer" --to projectgit add .magpie && git commit -m "Add our note on pdfkit"

Or copy one of your own notes there: repomagpie adopt pdfkit. When a teammate's agent is about to run npm install pdfkit, the hook asks them first, and their search and suggest find the note too. Anyone who can read the repository can read its notes.

In repomagpie ui, the Project view names the repository and says whether its shared notes are committed and pushed.

[The Project view in repomagpie ui: acme/checkout on github.com and "Shared notes are committed." above the project journal's three notes; zod is open, and says your personal journal has a note on it too]

The local app

repomagpie ui opens your journals in the browser. Search lists your notes before you type, and Import takes a list you paste. Review an inbox note: write the Verdict, set kind, domains, tags and rating, and press Ctrl+Enter.

[The inbox review in repomagpie ui: the Verdict being typed for Understand-Anything, with ai and tooling outlined as suggested domains, and tags to pick below]

Check a package: what your journals say before an install, and what the hook does in each agent.

[Check a package in repomagpie ui: pdfkit's avoid note says the hook asks first or stops the first try, depending on the agent; left-pad has no note, so the hook stays silent]

Suggest for this project: the notes that fit, and why each one is a candidate.

[Suggest in repomagpie ui: microsoft/playwright first, matched on the @playwright/test dependency; pdfkit listed last as in use with an avoid note, with pdf-lib and puppeteer instead]

See a journal as a graph: notes, their tags, [[links]] and alternatives, coloured by domain if you choose. Click a note to read and edit it beside the graph.

[The graph page in repomagpie ui, coloured by domain: 42 notes, 13 tags and 75 connections; the most connected, such as #self-hosting, #ai-agents and #frontend, listed beside it]

How it compares

A line like "avoid pdfkit" in CLAUDE.md covers one project. A RepoMagpie note works across projects, shows up in search, and the hook checks it on every install. It isn't session or conversation memory: it remembers your decisions about tools, which you write. A star list or an awesome list holds no opinion your agent can use; a note does. RepoMagpie isn't a scanner: it never claims to detect malware or vulnerabilities, so run one next to it (vision).

FAQ

Documentation

• Spec: every command, flag and --json document (repomagpie --help lists the commands)
• Agents: what each coding agent supports, and setting up by hand
• Note schema: the format of a note
• The local app: screens, API and security rules
• Testing the beta: the steps for a week with the beta, and how to send feedback
• Vision, competitors and decisions

Open an issue for bugs and ideas. The project doesn't take pull requests yet (CONTRIBUTING.md). To report a vulnerability, see SECURITY.md.

Licence

MIT © 2026 Yusuf Suat Babacan