agentping

name

agentping

description

Reach the human out-of-band when you are blocked and they may be away from the chat. Sends a real OS notification (or phone push / Slack / custom channel) and can block for the reply: a free-text answer, an approve/deny decision, or a pick-one choice. Use when you need approval before a risky or irreversible action, when you hit an ambiguous decision only the user can settle, when a long task finishes and needs sign-off, or when the user says "ping me", "notify me", "ask me when", "let me know", or "get my approval". Works from any agent that can run a shell command (Cursor, Claude Code, Codex, OpenClaw, Hermes).

agentping

A single-file CLI that pings the human through their own notification settings and, when you ask, waits for their reply. Use it instead of stalling silently or guessing when you are blocked and the user might not be watching the chat.

Invoke it by path so it resolves the same from every agent:

AN="$HOME/.local/bin/agentping"   # or wherever install.sh put it

If it is not on PATH, call the script directly (e.g. the cloned repo path) or python3 /path/to/agentping.

When to reach for it

• Approval gate before something risky or irreversible (deploy, delete, spend, force-push, schema change).
• Blocking decision you genuinely cannot infer from the task or the code.
• Done, needs sign-off: a long-running task finished and the next step needs a human.
• The user explicitly asked to be pinged, notified, or asked.

Do not use it for things you can decide yourself, or to narrate progress. One ping should carry a real question or a real decision.

The four verbs

# Fire-and-forget banner (no reply expected)
 notify  --title 


answer=


  confirm  ; 
  run_migration

   



pick=