Agent Ping

Let any AI agent tap you on the shoulder.

Install · Verbs · Channels · MIT

When an agent is blocked and needs your approval, an answer, or a decision, it pings you through your normal notification settings and waits for your reply. No more coming back to a chat that has been idle for an hour because the agent was too polite to interrupt.

One file, no dependencies (Python 3.8+ standard library only), works from any agent that can run a shell command: **Cursor, Claude Code, Codex, OpenClaw, Hermes**, or your own scripts.

# the agent runs this and blocks until you tap a button on your Mac/Linux/Windows:
agentping confirm "Run the destructive migration on prod?" && ./migrate.sh

---

Why

Agents stall silently or, worse, guess. Both are bad. Agent Ping gives them a reliable out-of-band channel to you:

• Approval gates. Pause before anything risky or irreversible.
• Real questions. Get the one answer the agent genuinely cannot infer.
• Sign-off. "The long job finished; what next?"
• Away from the keyboard? Route the ping to your phone and reply from there.

The agent always calls the same four verbs. **You** decide where the ping lands: desktop, phone, Slack, or a command of your own. That indirection is the whole idea: the *notification linkup* lives in your config, not in the agent.

Install

**npm** (one command; gives you the `agentping` command):

npm install -g agentping

Agent Ping is one Python file, and the npm package is a thin launcher around it, so you need **Python 3.8+** on your `PATH` (point `AGENTPING_PYTHON` at a specific interpreter if `python3`/`python` isn't it). No Pyth