magpieSnap
Press Print Screen, drag a box around the problem, type a note, press Enter. The screenshot, your note, and which app and window it came from land in your Claude Code session. No saving, dragging or pasting.
You already know what's wrong: you're looking at it. magpieSnap gets that picture, and what you'd say about it, into Claude's context in the time it takes to press Enter.
Every display freezes. magpieSnap has already noted which window you were in: Chrome and the page title, or the app's name.
Around the problem, on any monitor. Or click once to send the whole screen.
"The price is cut off on narrow screens." Running more than one Claude session? Pick which one gets it.
When Claude is done it says so, and a notification tells you what changed, so you know to reload and look.
Not just a picture. Claude gets what it needs to find the code behind it.
Type "fix it", or nothing at all with channels on. When Claude calls magpie_done, its one-line summary pops up on your screen.
› fix it ⎿ magpie hook: capture #k3f9 attached ⏺ magpie_get(id: "k3f9") Note: the price is cut off on narrow screens From: Google Chrome, page "Checkout · My Shop" Boxed a 412x96 area on a 1920x1080 screen. ⏺ The total column has a fixed width. Letting it grow: Update(src/components/CartItem.css) + .price { min-width: max-content; } ⏺ magpie_done(id: "k3f9", summary: "Prices no longer clip in the cart: .price grows to fit")
Browser extensions only see web pages. magpieSnap sees what you see, and tells Claude which window it was.
Chrome, Edge, Firefox. Claude gets the page title with it, so it knows which page you mean before it opens a file.
An Electron app, a WPF dialog, a settings window that lays out wrong at 150% scaling. Claude hears the app, the window and the scale.
A HUD that overlaps, a sprite drawn in the wrong spot. Run it windowed or borderless and capture it mid-frame.
All displays freeze at once, each at its own resolution and scaling. Box the problem on whichever one it's on.
A crash dialog you can't copy from, a stack trace in someone else's terminal. Box it and Claude reads it.
Each Claude Code session registers its project folder. Pick the session in the overlay; it remembers your last pick.
A capture is never handed to Claude twice, whichever way it arrives.
A Claude Code prompt hook adds any waiting capture to the next thing you type in that project, even a bare "fix it". Works in a terminal, in your IDE, and in the Code tab of the Claude desktop app.
With Claude Code channels on, the capture arrives right away and Claude starts on it without you typing anything. Needs Claude Code in a terminal, started with:
claude --dangerously-load-development-channels server:magpie
newVersion 0.1.0 for Windows 10 and 11 (64-bit). Free under the MIT license.
Installs to Program Files, adds Start menu and desktop shortcuts, and starts the tray app.
Download installer 76 MBYour settings file is backed up first. Uninstalling takes all three out again.
magpieSnap isn't code-signed yet, so Windows SmartScreen may say "Windows protected your PC". Click More info, then Run anyway. To check the download: certutil -hashfile magpieSnap-0.1.0-x64.exe SHA256.
About two minutes, no terminal needed. You need Claude Code: in a terminal, an IDE, or the Code tab of the Claude desktop app.
Run the installer. A magpie appears in your system tray.
Click the welcome notification, or right-click the tray icon and choose Connect to Claude Code…. It works with or without the claude command on your PATH.
Or open a new session. Each session that starts with magpieSnap connected shows up in the tray menu and in the overlay's Send to list.
Box something, type a note, press Enter, then go back to Claude and say "fix it".
Three MCP tools. Claude reaches for them on its own when a capture shows up.
| Tool | What it does |
|---|---|
| magpie_get | The close-up, the whole-screen view with the box marked, the note, and the source app and window. Without an id, the newest capture waiting for this project. |
| magpie_list | Recent captures: pending, seen or fixed, and which session they went to. |
| magpie_done | Marks a capture fixed with a one-line summary, which pops up on your screen. |
To a folder on your PC, %APPDATA%\Magpie\captures, and from there into your Claude Code session when Claude opens them, the same as an image you paste. magpieSnap has no server and sends nothing anywhere else. Open captures folder in the tray menu takes you there; delete them whenever you like.
You can, but then you're saving, switching windows, pasting and explaining which app and page it is. magpieSnap does all of that in one keypress and a sentence, adds a whole-screen view so Claude sees the surroundings, and gets Claude to tell you when it's fixed.
Yes, in the Code tab: captures ride along with your next message there. Pushing a capture in without typing (channels) needs Claude Code in a terminal for now.
The one you pick in the overlay's Send to list. It defaults to the one you sent to last. If no session is running, the capture waits and goes with your next message in that project.
Yes. Press Enter on an empty note and the screenshot is the whole message.
Some games in exclusive full-screen mode can't be captured by any screen grabber. Switch the game to windowed or borderless windowed and it works.
Uninstall magpieSnap from Settings → Apps. The uninstaller takes the MCP server, the prompt hook and the tool permission out of Claude Code too. Your captures stay in %APPDATA%\Magpie until you delete the folder.
Windows only for now.
Nothing. magpieSnap is free under the MIT license.
