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

@adeildo/pi-harness

v5.12.0

Published

Every adeildo Pi extension in one install: the permission dialog, the look, the providers, the questions, the skill calls the session tasks and the context pruning. Each is its own extension, so pi config turns one off.

Readme

What comes in it

| Piece | What it does | | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | | Permission | Asks before a command runs, with a note the model reads. A model answers the easy ones for you | | Questions | The model asks instead of guessing, with options, a preview of each, a note on any and your own answer | | Tasks | Keeps what the session is doing, what it did and with what result, what waits on you, and what was decided | | Compact | Hides old tool output in long sessions to cut what each request costs, and writes pi's compaction summary from the tasks | | Peers | Agents in the same folder see each other's work, talk in a room, hear what you tell everyone, and split what you ask anyone | | Skill calls | Call the skills you already have from anywhere in a message, several at once, shown as chips | | Look | The start screen, the editor with the branch and the model on its borders, and a box around each command | | Providers | Bills Anthropic OAuth requests to your Claude plan, and keeps several accounts per provider |

All of them are on once the package is installed.

[!WARNING] Providers makes Pi introduce itself to Anthropic as Claude Code whenever a request uses an Anthropic OAuth token. Using a subscription from anything other than Claude Code may break Anthropic's terms. Turn it off, as below, if you do not want that. A request with an API key goes out untouched.

Turning a piece off

Each piece is its own extension in this package, so pi config switches off the one you do not want, globally or for one project. The settings file has a switch per feature too, read on the next /reload, and the feature ids are permission, look, subscription, accounts, questions, skills, tasks, compact and peers.

{ "features": { "subscription": { "enabled": false } } }

To have only one piece, install its own package instead. With both installed, the first copy that loads runs the feature and the other stays off.

Settings

Alt+S opens the settings of every piece. They live in ~/.pi/agent/extensions/pi-harness/settings.json, and each piece's page lists its own. A setting marked project is also read from .pi/extensions/pi-harness/settings.json in a project Pi trusts, where the project value wins.

The whole set, with the pictures and the settings of each piece, is in the root README.

Part of pi-harness, which is every piece in one install.