Notify
Extension
Sends a fixed ‘ready for input’ notification through Windows, Kitty, or OSC-compatible terminal protocols.
What it does
After Pi emits agent_end, this extension sends the fixed title Pi and body Ready for input through one terminal notification path.
It selects a Windows toast when WT_SESSION is present, Kitty OSC 99 when KITTY_WINDOW_ID is present, and OSC 777 otherwise.
When to reach for it
Invocation: Load the extension; its agent-end hook runs automatically.
- A Pi run may finish while the terminal is not in view
- Request a generic ready-for-input signal from a compatible notification client.
- A completion alert should avoid session details
- Use the fixed title and body instead of including prompt, response, file, or task content.
What it adds
- Environment-based routing among PowerShell, Kitty OSC 99, and OSC 777.
- A fixed completion message that does not include session content.
How it fits
- Pi Watcher: Pi Watcher can initiate focused agent turns from editor markers; Notify adds a generic signal when an agent run ends.
Common questions
- What are its limitations?
- Routing is heuristic: WT_SESSION chooses Windows, KITTY_WINDOW_ID chooses Kitty, and every other environment receives OSC 777 whether or not the terminal supports it. The extension does not report notification failures, and this local copy runs on agent_end.
It’s working if
- After an agent run ends, a compatible notification client displays Pi and Ready for input.
- The selected branch invokes PowerShell or writes the expected OSC sequence; the extension has no separate success indicator.
Source and setup
Provenance
- Project
- Notify
- Origin
- Fero
- Current maintainer
- Vedang Manerikar
- Relationship
- adopted
- Installed source
pi-extensions/notify.ts- Source path
- View source (
pi-extensions/notify.ts) - Compatibility
- Windows Terminal and PowerShell
- Kitty
- OSC 777-capable terminal
- License
- MIT
- License publication scope
- Independently written catalog summary plus source link and upstream attribution; retain MIT attribution.
- Reviewed revision
9a0af933d90ad9175eca0ff27db6624c5d6bb4fe- Catalog revision
e0c035a297462c519315abfa1af31a1ed3bd9eef
Setup notes
- Adopted from the MIT-licensed Pi example originally implemented by Fero; Vedang maintains this local copy.
- The installed source is a local Pi extension that registers an agent-end hook.
- The Windows route needs WT_SESSION and PowerShell, the Kitty route needs KITTY_WINDOW_ID and OSC 99 support, and the fallback needs OSC 777 support.