Agents overview
Which agents GreatPing supports, what each one alerts you about, and how the integration works.
greatping setup connects GreatPing to the coding agents on your computer. After that, the agent alerts you by itself when it waits for you; you do not have to ask it to.
What each agent alerts on
Agents tell the outside world different things about themselves, so coverage differs. GreatPing only alerts on what an agent reliably reports, and never guesses.
| Question | Permission | Input form | Finished turn | |
|---|---|---|---|---|
| Claude Code | Yes | Yes | Yes (MCP dialogs) | Optional, off by default |
| Codex | No | No | No | Yes, on by default |
| OpenCode | Yes | Yes | No | Yes, on by default |
| Pi | Extension dialogs | No | Extension dialogs | Yes, on by default |
| Cursor | No | No | No | Yes, on by default |
Where an agent has no automatic alert for something, it can still reach you on request: say "ping me when you need me" and it uses GreatPing's tools. See Ask in plain words.
How it works
greatping setup adds three things to each agent you choose, in the agent's own settings:
- Hooks or an adapter that watch for the agent waiting on you. They report only which agent waits and why; nothing from the prompt, the command or your files leaves the computer.
- MCP tools (
notify,ask_user,get_status,pause_alerts,resume_alerts), so the agent can message you, ask you something or pause alerts when you ask it to. See MCP tools. - The GreatPing skill, which teaches the agent when to use those tools. See Ask in plain words.
The hooks only observe. They never answer a question, approve a permission or slow the agent down: if GreatPing cannot be reached, they give up quietly within a few seconds and the agent carries on.
An alert ends by itself when you answer at the computer, send your next message, or the session ends.
Set up, check, remove
greatping setup # choose agents interactively
greatping setup claude # one agent
greatping doctor # check that every hook runs
greatping status # pairing, devices and agents
greatping setup codex --removesetup shows a plan of what it will change and writes nothing until you apply it. It keeps your other hooks, tools and settings as they are. Restart running agent sessions afterwards so they load the hooks.
The app shows each computer's agents and their state on the computer's screen: Automatic, On Request, Not Set Up or Needs Repair. See Computers.
Apps built on these agents
Desktop and web apps that run Claude Code or Codex underneath, such as T3 Code with Claude Code, use the same settings and hooks, so GreatPing alerts there too. Set the agent up with greatping setup on the computer where the app runs its agent.
Silence one session
To keep a single terminal or session from alerting, start it with:
GREATPING_DISABLE=1 claudeAutomatic alerts stay off for that process; explicit commands such as greatping notify still work. To silence the whole computer for a while, use greatping pause 2h.
Requirements
- The
greatpingcommand line tool, paired withgreatping login. See the Quick start. - Node.js 22.20 or later, available as
nodeto the agent. - Install Node and GreatPing in a stable place. Setup refuses paths that change with every Node update, such as a version manager's per-shell folder, because the hooks would break after the next update.
greatping doctorreports hooks tied to one Node version.
Tested on macOS with Claude Code 2.1, Codex 0.160, OpenCode 1.18, Pi 0.85 and Cursor 3.20. Linux and Windows use the same integrations but have been tested less.
GreatPing