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

pinecall

v0.9.52

Published

The pinecall CLI: an agent's project in any language — prompt, chat, test, simulate, start, deploy — against the Pinecall gateway

Readme

pinecall

The CLI for Pinecall agents: link a project to your org, print the prompt a state produces, chat with the agent in a terminal, run its goldens, and start the process that answers its calls — for an agent written in TypeScript (@pinecall/agents) or Ruby (pinecall gem).

Install

npm i -g pinecall                 # once per machine, whatever the agent is written in

The CLI never loads your class. It starts your project's own serve entry — @pinecall/agents/serve for TypeScript, Pinecall::Serve for Ruby, python -m pinecall.serve for Python — and drives it through the gateway, so the SDK that runs is the version your project pinned. A project depends on its SDK, never on this CLI.

Quick start

pinecall new front-desk          # or --ruby, --python: a project of one agent, ready for every verb below
cd front-desk && npm install     # bundle install for Ruby, uv sync for Python
pinecall link        # sign in through the browser; writes your key to ./.env
pinecall prompt      # the prompt the model reads, offline; --state <golden> for another state
pinecall chat        # talk to the agent in this terminal
pinecall test        # run the goldens
pinecall start       # run the agent: the process you deploy
pinecall deploy      # or let Pinecall run it
pinecall mcp install # or do all of it from Claude Code, Codex, Cursor…

Every verb acts in the sandbox unless --prod is given. The CLI reads PINECALL_KEY and PINECALL_URL from the environment or the project's .env.

| | | |---|---| | docs/quickstart.md | nothing to an agent that answers, in ten minutes | | docs/the-cli.md | every verb | | docs/the-mcp.md | pinecall mcp: the same CLI as an assistant's MCP server, and mcp install | | Deploy to Pinecall | pinecall deploy: Pinecall installs and runs your project | | ARCHITECTURE.md | the CLI file by file |

Development

pnpm install         # links ../agents, the framework's checkout, when its version fits
pnpm test
pnpm lint
scripts/check        # build, lint, test — what CI runs

License

Apache-2.0, including its patent grant. No CLA.