npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@rbright/pi-notify-desktop

v0.1.1

Published

OSC desktop notifications for Pi agent turn completion.

Downloads

174

Readme

pi-notify-desktop

CI

pi-notify-desktop sends terminal OSC notifications when the Pi agent finishes a turn and is waiting for your next input.

npm package: @rbright/pi-notify-desktop

Install into Pi (GitHub)

Global install:

pi install git:github.com/rbright/pi-notify-desktop

Project-local install (writes to .pi/settings.json in the current repo):

pi install -l git:github.com/rbright/pi-notify-desktop

After publishing to npm, you can also install from npm:

pi install npm:@rbright/pi-notify-desktop
pi install -l npm:@rbright/pi-notify-desktop

If Pi is already running, reload extensions:

/reload

Quick check: run a short prompt (for example, reply with ok) and wait for completion.

Compatibility

| Terminal / Mux | Auto Protocol | Status | | --------------------------------------------- | ----------------------- | ------ | | WezTerm | OSC 9 | ✅ | | Ghostty | OSC 777 | ✅ | | iTerm2 | OSC 9 | ✅ | | tmux (inside supported terminal) | passthrough + OSC 9/777 | ✅* | | zellij (parent terminal = WezTerm) | OSC 9 | ✅ | | zellij (parent terminal = Ghostty) | OSC 777 | ✅ | | zellij (parent terminal hidden by layout/env) | OSC 9 fallback | ✅ |

* tmux requires passthrough:

set -g allow-passthrough on

Behavior

No configuration is required.

  • Triggers on final assistant message_end (non-tool stop reasons)
  • Falls back to agent_end if message-based completion is missed
  • Writes OSC to /dev/tty first, then to stdout when needed
  • Selects protocol automatically:
    • iTerm2 / WezTerm → OSC 9
    • Ghostty → OSC 777
    • zellij with hidden parent-terminal context → OSC 9 fallback
    • everything else → OSC 777

Troubleshooting

  1. Confirm install: pi list
  2. If Pi was open during install/update, run /reload
  3. Run a simple prompt and wait for completion
  4. In tmux, confirm set -g allow-passthrough on
  5. In non-TTY mode (for example pi -p "hello"), notifications are intentionally skipped

Development

just deps
just lint
just typecheck
just test
just check
just precommit-install
just precommit-run

Run the extension directly during local development:

bun install
pi --no-extensions -e ./src/index.ts

Publishing (npm)

Manual publish (@rbright/pi-notify-desktop):

bun run check
npm publish --access public

Automated publish is available via GitHub Actions (.github/workflows/publish.yml) and runs on:

  • workflow_dispatch
  • tag pushes matching v*

Required repository secret:

  • NPM_TOKEN (npm automation token with publish permission)