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

@nonbot/cli

v0.9.0

Published

The local host for non.bot ▶ Run — opens a terminal on your machine and starts the work in your linked repo.

Downloads

2,773

Readme

@nonbot/cli

The local host for non.bot ▶ Run. Install it, log in once, and leave the daemon running — when you click ▶ Run on a story in non.bot, a terminal opens on your machine and starts the work in your linked repo.

npm install -g @nonbot/cli
nonbot login
nonbot daemon

How it works

The daemon runs as an ordinary process in your shell. It polls non.bot for Runs you've started, and when one arrives it opens a terminal in your linked repository and launches your CLI agent (claude, codex, or gemini). Because it's a plain Node process, it uses your existing PATH and whatever CLI logins you already have — no extra setup.

Getting started

# 1. Install
npm install -g @nonbot/cli

# 2. Create a Personal Access Token on non.bot
#    Settings → Connections → API tokens → "New token"

# 3. Log in (paste the token when prompted)
nonbot login

# 4. Leave the daemon running in a terminal tab
nonbot daemon

# 5. Click ▶ Run on non.bot — a terminal opens and starts the work.

Non-interactive login (for CI or scripting):

nonbot login --token "$NONBOT_PAT"

Commands

nonbot login            Log in with a Personal Access Token
nonbot daemon           Run the poll loop and launch terminals (the main command)
nonbot run <id>         Launch a single Run by id, then exit
nonbot status           Show login + daemon status
nonbot doctor           Health check — auth, server, providers, terminal
nonbot logs             Show recent local Run launches
nonbot profiles         List configured accounts
nonbot test             Print a local diagnostic banner (no server needed)
nonbot --help           Full command list
nonbot --version        Print the version

Useful flags

| Flag | Effect | |---|---| | --headless | Run inline without opening a terminal window (daemon, run) | | --profile <name> | Use a named account instead of the default | | daemon --install / --uninstall | Run the daemon automatically at login |

Terminals

On macOS the daemon launches Terminal or iTerm; on Linux it uses your system terminal; on Windows it uses Windows Terminal. If you run the daemon inside a tmux session, Runs open as new tmux windows instead of separate terminal windows.

Override the terminal with NONBOT_TERMINAL (e.g. NONBOT_TERMINAL=iterm), or set a preferred terminal in your non.bot settings.

Configuration

Credentials are stored in ~/.config/nonbot/auth.json (file mode 0600). Override the config directory with NONBOT_CONFIG_DIR.

If a token is lost or compromised, rotate it at non.bot → Settings → Connections → API tokens.

Requirements

  • Node.js 18 or newer
  • A non.bot account with a linked repository

License

Proprietary — all rights reserved. See LICENSE. This package is published to npm solely to function as the local host for non.bot ▶ Run; it is not open-source software.