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

get-an-expert

v0.1.0

Published

Live terminal chat with a human expert from Get An Expert. Run: npx get-an-expert chat <requestId>

Readme

get-an-expert

Live terminal chat with a human expert, from Get An Expert.

When a Get An Expert session is escalated to a human, this opens the chat:

npx get-an-expert chat <requestId>

It's a plain, private, human-to-human conversation — like texting:

  • Type to talk. [you] is you, [<expert name>] is the expert.
  • No AI reads this chat. The only automation that touches your messages is a local secret redactor (keys/tokens are scrubbed on your machine before anything is sent, and again server-side).
  • /end — end the session for good, from your side. The server refuses anything further the instant either side ends.
  • /pause [minutes] — pause session relaying (once relay ships) without ending the chat; /pause off resumes.
  • Closing the window does NOT end the session — rejoin with the same command, or use /end to end it.

The chat token comes from the escalation flow (~/.get-an-expert/relay.json), or pass --token <chatToken> / set GET_AN_EXPERT_CHAT_TOKEN yourself. Point at a different backend with GET_AN_EXPERT_API_URL.

Session relay

While your chat is open, your working session (prompts, your agent's replies, agent-run commands with their output, file edits) relays live to the expert so they can watch real attempts instead of retellings — that's what you consented to at escalation. Wiring per editor:

npx get-an-expert init claude-code   # relay script only; hooks ship with the plugin
npx get-an-expert init cursor        # + wires ~/.cursor/hooks.json
npx get-an-expert init windsurf      # + wires ~/.codeium/windsurf/hooks.json

init copies a standalone relay script to ~/.get-an-expert/relay.mjs and adds observe-only hook entries (your existing hooks are preserved; a .gae-backup copy is kept). The hooks are inert unless ~/.get-an-expert/relay.json exists — that file appears when you consent to an expert chat and disappears the moment it ends, from either side. Every relayed payload passes local secret redaction before leaving your machine.

Terminal A shows a subtle ⟢ your last run is visible to <expert> line as events land. Known limitation: Windsurf's hooks don't expose command output, so the expert sees the command line only there.

Everything auto-deletes after 30 days and is covered by the request's private deletion link. Privacy: https://get-an-expert.vercel.app/privacy