You start a task in your coding agent, tab over to answer a Slack message, and forget you ever asked it anything. Fifteen minutes later you remember, tab back, and the agent has been sitting there since minute two, quietly waiting for you to approve a permission prompt it fired the moment you looked away. That specific, avoidable waste of time is the entire reason peon-ping exists.
Quick facts
License: MIT. Primary language: Shell. Last active: 29 May 2026 (as of 4 July 2026).
What it is
peon-ping is a command-line tool that hooks into AI coding agents, meaning Claude Code, Codex, Cursor, and a long list of others, and plays a sound or shows a banner whenever something worth your attention happens: the agent finishes a task, hits an error, needs permission, or gets ignored for too long. By default those sounds are Warcraft III peon voice lines: "Ready to work?", "Work, work.", the annoyed "Me not that kind of orc!" if you click it one too many times. It also throws up a large on-screen banner and changes your terminal tab title, so even with the sound off you can tell at a glance which of your five open windows just needs you.
The real-world problem it solves
AI agents don't tell you when they're stuck. They just sit there. If you're mid-refactor and switch over to read documentation, there's no natural signal pulling you back the second the agent needs a yes or no. You either babysit the terminal, which defeats the point of delegating the work, or you drift off and lose ten or fifteen minutes before you notice the cursor's been blinking at an unanswered prompt. peon-ping closes that gap with something your ears pick up before your eyes do.
Where it's useful
A backend developer running a long test suite through Claude Code sets different sound categories for pass versus failure, so a crash gets an irritated growl instead of the same cheerful "done" chime as a clean run, and they know which one it was before they even look up.
A freelancer juggling three client codebases in three terminal tabs uses peon-ping's path rules to bind a different voice pack to each project folder, so a StarCraft line means Client A pinged them and a Warcraft line means Client B did, no glance at the tab required.
Someone running an agent on a remote dev box over SSH starts the built-in audio relay so sound generated on the remote machine plays back through their local speakers, instead of vanishing into a headless server nobody's listening to.
A team building their own tools on top of Claude Desktop or Cursor's MCP support wires up peon-ping's MCP server directly, so the agent itself decides which line to play, like reaching for a StarCraft "Nuclear launch detected" the moment a deploy script actually nukes something instead of playing the same generic alert every time.
Why it stands out
The project's creators say peon-ping is what pushed Microsoft to add native sound hooks to VS Code, a change reaching more than 50 million users, which is a fairly unusual arc for something that started as a joke about orc voice lines. It also formalized its own approach into an open spec, the Coding Event Sound Pack format, so any agentic IDE can adopt the same categories rather than everyone inventing their own notion of "task finished" from scratch.
The pack library backs that up: over 160 community-contributed voice sets spanning Warcraft, StarCraft, Portal, Red Alert, Team Fortress 2, and more, each one added by a different GitHub contributor rather than the core team alone. And the configuration goes well past "on or off": you can silence specific directories, bind packs to specific IDEs, run headphones-only mode, or even respect macOS Focus so a notification doesn't blast out mid-meeting. It's a small tool that clearly got used hard enough by its own maintainers to sand down every annoying edge case.
There's also a genuinely odd bonus feature bolted on: Peon Trainer, which nags you to do pushups and squats between coding sessions using the same voice lines. It's a strange pairing on paper, and it works because it piggybacks on infrastructure that's already watching your session anyway.
How to get started
The fastest path is one line in a terminal:
curl -fsSL https://raw.githubusercontent.com/PeonPing/peon-ping/main/install.sh | bash
Homebrew users can run brew install PeonPing/tap/peon-ping followed by peon-ping-setup. Either way, peon setup launches an interactive wizard that walks through volume, which event categories to enable, notification style, and where banners appear on screen, and you can rerun it any time your preferences change. From there, swapping voice packs, muting sounds during a meeting, or renaming a session is a single peon command away.
Takeaway
peon-ping is a small utility solving a problem most people didn't realize they'd normalized: sitting there refreshing a terminal because nothing tells you when an AI agent actually needs you. That it did this well enough to reportedly influence how a 50-million-user editor handles the same problem says the itch was real, not just a Warcraft nostalgia trip.