Your AI Agent Finished 15 Minutes Ago. You Didn't Notice.

You know the drill. You kick off a coding agent, switch to another tab to do something useful, and then completely forget you're waiting on it. When you finally come back, the agent has been sitting idle for fifteen minutes waiting for permission to continue. peon-ping is an open-source project that fixes this by playing Warcraft (and StarCraft, Portal, Zelda, and more) character voice lines and throwing up bold on-screen banners whenever your AI coding agent needs your attention.

What It Does

peon-ping hooks into your AI coding agent and fires off notifications when the agent finishes a task or needs you to approve something. Instead of a quiet system ping you'll ignore, you get game character voice lines and visual overlay banners that are hard to miss. The sound roster pulls from Warcraft, StarCraft, Portal, Zelda, and other franchises, so your build failures can be announced by a peon and your completed tasks by someone a little more dignified.

It works with a long list of agents and IDEs — Claude Code, Amp, GitHub Copilot, Codex, Cursor, OpenCode, Kilo CLI, Kiro, Kimi Code, Windsurf, Google Antigravity, Rovo Dev CLI, DeepAgents, Qwen Code, iFlow CLI, Trae, Kiro IDE, ECA, and any MCP client. For Claude Code it registers as a hook; for the rest, it uses adapters. There's also an MCP server so the agent itself can pick its own sound. It runs on macOS, Linux, WSL2, Windows, MSYS2, and over SSH, and it's MIT licensed.

Why It's Cool

The problem is real and the solution is proportionate. Most notification tools are either too subtle (a badge you never see) or too aggressive (full-screen takeovers). peon-ping lands in the middle with audio plus a banner — enough to pull you back without derailing you.

• It meets you where you already are. The adapter list is genuinely broad. If you've got a favorite agent or IDE, there's a decent chance it's covered, and the MCP server path means anything MCP-compatible can participate too.

• The agent can choose its own sound. That MCP server detail is the clever bit. Rather than every notification sounding identical, the agent can pick a line that fits the situation — which is a small touch that makes the whole thing feel less like a dumb alert and more like feedback.

• Remote and container workflows are handled. SSH, devcontainers, and Codespaces are called out explicitly, and there's even mobile notification support. That matters, because the people who tab away from an agent most often are the ones running it somewhere other than their laptop.

• WSL2 audio gets actual attention. The README notes that on WSL2, peon-ping plays audio on the Windows side and probes your Windows host to pick the best playback path (cached per Windows build). That's the kind of unglamorous detail that separates a toy from something you'll leave installed.

• It's configurable and extensible. There are sound packs, a guide for creating your own, quick controls, a debug mode, and a "Peon Trainer" section if you want to go deeper. You're not locked into the default set.

How to Try It

The recommended path is Homebrew:

brew install PeonPing/tap/peon-ping

Then run setup to register hooks and download the sound packs:

peon-ping-setup

This works on macOS and Linux. If you're on macOS, Linux, or WSL2 and prefer a script:

curl -fsSL https://raw.githubusercontent.com/PeonPing/peon-ping/main/install.sh | bash

One heads-up for WSL2 users: the first run probes your Windows host to figure out the best audio path, and that result is cached. If audio misbehaves, check the debugging section of the README before assuming something's broken.

From there, the README walks through configuration, quick controls, the MCP server, multi-IDE setup, remote development, mobile notifications, and sound packs. There's also a Korean, Chinese, and Japanese translation of the README if that's useful to you.

The repo lives at github.com/peonping/peon-ping, and there's a demo video and site at peonping.com if you want to see it in action before installing.

Final Thoughts

peon-ping is a small, focused tool that solves one specific annoyance well. It won't change how you write code, but if you've ever lost fifteen minutes because an agent was waiting on you and you didn't know, it'll pay for itself quickly. The broad adapter support and the MCP server make it more than a novelty — and the fact that it handles WSL2 audio and remote environments suggests the maintainers actually use it themselves. If you work with AI coding agents regularly, it's worth a few minutes to install and see whether the notifications fit your workflow.