GreatPingOpenCode and Pi
How GreatPing alerts you from OpenCode and Pi, what each one covers, and how to set them up.
GreatPing ships native adapters for OpenCode and Pi inside the command line tool. Setup installs them from your computer; nothing else is downloaded.
Set up
greatping setup opencode
greatping setup piRestart the agent afterwards. Pi must be installed and on your PATH, since setup uses Pi's own pi install.
Supported versions: OpenCode 1.18.34 or later in the 1.x line (OpenCode 2 has a different plugin system and is not supported yet), and Pi 0.85.1 or later before 1.0. Setup refuses other versions and tells you.
What alerts you
| Moment | OpenCode | Pi |
|---|---|---|
| A question waits for you | Has a question for you | Extension dialogs that block the agent |
| A permission waits for you | Needs your approval | Not reported by Pi |
| The response is finished | Finished its turn, once per response | Finished its turn, once Pi has fully settled |
The alert clears when you answer at the computer or start your next message. Failed or cancelled responses, and work done by sub-sessions, do not alert you.
Finished-turn alerts are on by default; greatping setup opencode --no-finished (or pi) turns them off.
Tools
- OpenCode gets GreatPing's MCP tools and the skill added to its configuration. Your own config files are not rewritten.
- Pi gets the same tools as native Pi tools (
greatping_notify,greatping_ask_userand so on) and the skill.
Silence one session
GREATPING_DISABLE=1 opencode (or pi) turns automatic alerts off for that session; the tools still work.
Check
greatping doctor
greatping statusBoth report the adapters and when they last saw the agent.
Remove
greatping setup opencode --remove
greatping setup pi --removeRestart running sessions afterwards. Files you edited are kept, and the computer stays paired.