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

@juanbenjumea/pi-go-on

v0.1.2

Published

Goal-aware autonomous continuation for Pi conversations

Readme

pi-go-on

Goal-aware autonomous continuation for Pi. A single nudge or bounded auto burst asks Pi to keep advancing the user's original outcome, rather than treating "go on" as an open-ended request to invent more work.

Install

pi install npm:@juanbenjumea/pi-go-on

The extension does not start background work on its own. You explicitly start continuation with a shortcut or command.

Controls

| Control | Action | |---|---| | Ctrl+Alt+N (Alt+N fallback) | Send one goal-aware continuation prompt | | Ctrl+Alt+G (Alt+G fallback) | Start/stop auto mode; it nudges after each settled run | | /go-on mode | Start or continue auto mode | | /go-on-mode [on|off] | Explicitly control auto mode |

Press the burst shortcut again, run /go-on-mode off, or interrupt the active run to stop. Auto mode also disarms on completion, errors, aborts, repeated no-progress verbal turns, or after 15 nudges.

Continuation policy

Each nudge asks Pi to inspect what is complete, select one high-value next step toward the original outcome, and verify it. It treats the outcome and explicit deliverables as requirements without assuming the proposed means are; a better in-scope route is welcome, while creative intent should be preserved. It encourages deeper—not broader—work: check consequential assumptions against primary evidence, use concrete domain-appropriate methods, and seek independent or reproducible validation where useful. Cross-field techniques should address a specific weakness, not become role-play or extra deliverables. The agent should preserve the original scope, avoid repeating work or manufacturing adjacent tasks, and stop when blocked or when a real decision or approval is needed. It must not take high-impact actions such as deleting data, publishing, deploying, committing, or pushing without explicit authorization.

Auto mode is intentionally bounded and heuristic. The extension's completion detection is phrase-based; the model still decides whether the task is actually complete or blocked. Keep the burst limit and user-visible stop control in mind for long runs.

Migrating from a standalone file copy

If this extension is already loaded from a file path — for example an extensions entry in your Pi settings — remove that entry when you install the package. Pi tolerates the duplicate rather than failing: it disambiguates the command names (go-on-mode:1, go-on-mode:2) and reports no error. Both copies nevertheless stay active, registering the same shortcuts and both writing the go-on-mode status, so a burst can be armed twice. Enable exactly one copy.

Development

npm ci
npm test
npm run typecheck
./scripts/verify-load.sh   # uses node_modules/.bin/pi after npm ci
VERIFY_FROM_TARBALL=1 ./scripts/verify-load.sh   # what consumers install
./scripts/verify-release.sh   # verify a published release (needs network)

npm test mocks the extension API. scripts/verify-load.sh is the end-to-end counterpart: it starts a real Pi in RPC mode (the CLI bundled with the SDK dev dependency, or $PI_BIN/pi on PATH), loads this package through its manifest with an isolated agent directory and no network, and fails unless the /go-on-mode command is registered. With VERIFY_FROM_TARBALL=1 it first packs the package and loads the extracted tarball instead of the working tree, so a wrong files list or manifest cannot ship. CI runs both, and the publish workflow runs them again before npm publish.

scripts/verify-release.sh [version] checks a published release the way a consumer meets it: registry metadata, provenance attestation, downloaded tarball bytes against the registry shasum, working-tree parity, and a real runtime load of the published artifact. Run it after each release; maintainers can use it to confirm a release without trusting the build log.

For the one-time npm bootstrap and trusted-publishing setup, see RELEASING.md and run ./scripts/npm-release-setup.sh from a checkout. The wizard asks for confirmation before the initial irreversible npm publish and never stores credentials.

License

MIT