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

@hexdecimal16/nexo

v0.4.13

Published

nexo agent engine

Readme

nexo

npm version test

nexo is an AI agent that runs on your machine. It tracks what each run costs, scores the results, and keeps every run inspectable. You can use it from the terminal, from a web run inspector, or from Node code.

Requires Node 22.19 or newer.

Install

npm install -g @hexdecimal16/nexo
nexo init      # pick two models (s1, s2), store their API keys, make one test call

Running nexo for the first time also opens this setup. nexo update tells you when a newer version is out.

Everyday use

nexo                                            # chat; type /settings to change anything
nexo run "summarize this folder" --budget 0.25  # one task, then exit
nexo ui                                         # run inspector: traces, costs, scores
nexo cost --by day                              # what you spent
nexo doctor                                     # check Node, config, keys and tools

nexo --help lists every command. Data lives in ~/.nexo. Set NEXO_HOME to move it.

Settings and keys

Every option is in /settings inside a chat, or in nexo settings from the shell:

nexo settings keys                       # which keys are set and where from (never the values)
nexo settings set-key anthropic          # hidden prompt, or pipe the key on stdin
nexo settings set budgets.perRunUsd 0.5

Keys are stored in ~/.nexo/credentials.json (mode 600) and redacted from logs. A provider's environment variable, such as ANTHROPIC_API_KEY, takes precedence over the stored key.

Optional tools

Web search. Set a Brave Search or Tavily key and the agent gets a web_search tool. With both keys, it queries both and merges the results.

nexo settings set-key brave              # or tavily
nexo search "node 22 release notes"      # try it without a model

Browser control. The agent can drive your own Chrome, with your signed-in sites, through playwright-cli and the Playwright Extension. It keeps page snapshots on disk and reads only the lines it needs, so browsing uses few tokens.

npm install -g @playwright/cli@latest
nexo settings set-key playwright-personal   # paste the token from the Playwright Extension in that Chrome profile

Add one key per Chrome profile, such as playwright-work. First-run setup and /settings offer the same step. The browser skill tells the agent to ask before sending, posting, buying or deleting anything. Its wrapper also blocks the commands that run arbitrary code in your pages.

Use it from Node

import { createNexo } from "@hexdecimal16/nexo/sdk";

const nexo = createNexo();
try {
  const result = await nexo.run({ instruction: "Say hello", budgetUsd: 0.25 });
  console.log(result.output, result.costUsd);
} finally {
  await nexo.close();
}
  • Pass keys in code without writing them to disk: createNexo({ apiKeys: { anthropic: "…" } }).
  • nexo.keys(), nexo.setKey() and nexo.removeKey() manage stored keys. nexo.webSearch(query) searches without a model.
  • The SDK denies every tool approval by default, so a backend never waits on a person. Pass allowAll: true to createNexo or run to auto-approve tool actions in sandboxed environments. Always pass budgetUsd.
  • checkSetup() runs the doctor checks without starting the engine, for a start-up pre-flight.

Security

nexo's tools run shell commands and edit files. Path confinement is not a sandbox. If you run nexo for other people, give each request its own workspace and use a container for real isolation.

Develop

git clone https://github.com/hexdecimal16/nexo.git && cd nexo
npm ci
npm run nexo -- init     # run from source
npm run typecheck
npm test
npm run build            # release build into dist/
npm run bump -- patch    # set one version on every package

License

PolyForm Noncommercial 1.0.0. Free for any noncommercial use. Commercial use needs separate permission from the author.