@diegopetrucci/pi-notify
A pi extension that sends a notification when the agent is ready for input.
Package details
Install @diegopetrucci/pi-notify from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:@diegopetrucci/pi-notify- Package
@diegopetrucci/pi-notify- Version
0.1.18- Published
- Sep 1, 2026
- Downloads
- 857/mo · 65/wk
- Author
- diegopetrucci
- License
- MIT
- Types
- extension
- Size
- 16.5 KB
- Dependencies
- 0 dependencies · 1 peer
Pi manifest JSON
{
"extensions": [
"index.ts"
]
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
notify
A pi extension that sends notifications when the agent has fully settled and is waiting for input.
This started from the original notify.ts example in earendil-works/pi, but now supports multiple notification channels and JSON configuration.
Supported notification channels
Terminal notifications
- OSC 777: Ghostty, iTerm2, WezTerm, rxvt-unicode
- OSC 99: Kitty
Both are wrapped in tmux's DCS passthrough automatically when $TMUX is set;
see Running inside tmux.
Desktop notifications
- macOS Notification Center via
osascript - Linux desktop notifications via
notify-send - Windows toast notifications via
powershell.exe/ Windows Terminal / WSL
Bells and sounds
- terminal bell (
\a) - macOS sound playback via
afplay - Linux sound playback via
canberra-gtk-playorpaplay - Windows beep via
powershell.exe
By default, these channels are enabled:
- terminal notification
- desktop notification
- bell
Sound remains available as an opt-in option via config.
The extension automatically picks the appropriate backend for the current environment.
Install
Standalone npm package
pi install npm:@diegopetrucci/pi-notify
Collection package
pi install npm:@diegopetrucci/pi-extensions
GitHub package
pi install git:github.com/diegopetrucci/pi-extensions
Then reload pi:
/reload
Configuration
Config files are merged, with project config overriding global config:
~/<pi-config-dir>/agent/extensions/notify.json<project>/<pi-config-dir>/notify.json
Here <pi-config-dir> is Pi's runtime config directory name (CONFIG_DIR_NAME; .pi by default). Project config is only read after Pi reports that the project is trusted.
A ready-to-copy sample file is included at notify.example.json.
Example:
{
"enabled": true,
"onlyWhenInteractive": true,
"title": "Pi",
"body": "Ready for input",
"channels": {
"terminal": true,
"desktop": true,
"bell": true,
"sound": false
},
"terminal": {
"backend": "auto",
"tmuxPassthrough": "auto"
},
"desktop": {
"backend": "auto"
},
"sound": {
"backend": "auto",
"name": "Glass",
"linuxSoundId": "complete",
"frequencyHz": 1000,
"durationMs": 250,
"command": ""
}
}
Running inside tmux
Under tmux, terminal notifications need one line in your tmux.conf:
set -g allow-passthrough all
Without it, notifications never reach your terminal. tmux is the terminal emulator for the pane, so the escape sequence is delivered to tmux rather than to the terminal that can act on it. tmux has no OSC 777 or OSC 99 handler (checked in 3.7b, whose OSC dispatch covers 4/7/8/9;4/10/11/12/52/104/133) and does not forward OSC codes it does not recognise, so the notification is parsed and silently dropped. Desktop, bell, and sound channels are unaffected.
This extension therefore wraps terminal notifications in tmux's DCS passthrough
(ESC P tmux ; … ESC \), which asks tmux to forward the payload to the outer
terminal verbatim — but tmux only honours that when allow-passthrough is on.
Use all rather than on: under on, tmux only honours passthrough from panes
that are currently visible, which discards exactly the notification you want —
the one fired while you are looking at another window. The trade-off is that
all lets a program in any pane write bytes straight to the attached terminal;
notification sequences render nothing, but a malformed passthrough from a
background pane can garble the display, since those bytes bypass tmux's screen
model.
Set terminal.tmuxPassthrough to never to opt out of wrapping (for example if
your multiplexer forwards these codes itself), or always to force it when
$TMUX is not visible in the environment. Wrapping is safe to leave on auto:
with passthrough disabled in tmux, a wrapped sequence is dropped exactly like a
bare one, so nothing regresses.
Enable sound
Minimal example:
{
"channels": {
"sound": true
}
}
You can also customize the sound backend and options if needed.
Config fields
enabled: master on/off switchonlyWhenInteractive: skip notifications in print / non-UI modetitle: notification titlebody: notification bodychannels.terminal: enable terminal notification outputchannels.desktop: enable OS desktop notificationschannels.bell: enable terminal bellchannels.sound: enable sound playbackterminal.backend:auto,osc777,osc99,noneterminal.tmuxPassthrough:auto(wrap when$TMUXis set),always,neverdesktop.backend:auto,macos,linux,windows-toast,nonesound.backend:auto,macos,linux,windows-beep,command,nonesound.name: macOS system sound name, likeGlassorHerosound.linuxSoundId: freedesktop sound id, likecompletesound.frequencyHz: Windows beep frequencysound.durationMs: Windows beep durationsound.command: custom shell command whensound.backendiscommand
Notes
- Hooks the
agent_settledevent so automatic retries, compaction retries, and queued follow-ups do not trigger intermediate notifications. - Terminal notifications are wrapped for tmux when
$TMUXis set, which also requiresset -g allow-passthrough allintmux.conf. - Default message is
Pi/Ready for input. - Terminal, desktop, bell, and sound channels can be enabled independently.
- To opt into sound playback, set
channels.soundtotrue.