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

@workgraph/agent

v0.5.2

Published

Workgraph local agent — runs Claude jobs on your machine

Readme

@workgraph/agent

Local agent for Workgraph. Polls the cloud server for jobs and runs them against the Claude CLI on your machine — so your code never leaves your laptop.

Prerequisites

  • Node 20+
  • claude CLI installed and authenticated (claude /login works)
  • git configured for any private GitHub repos you want to document

Install

npm install -g @workgraph/agent
workgraph login

workgraph login defaults to the hosted Workgraph server at https://workgraph.space. Self-hosters can override with --url or the WORKGRAPH_SERVER_URL env var.

Commands

workgraph login                    # Pair this machine with your Workgraph workspace
workgraph login --dev              # Pair with a local dev server (http://localhost:3000)
workgraph login --url <url>        # Pair with a self-hosted instance
workgraph status                   # Show pairing status and agent info
workgraph logout                   # Remove local credentials
workgraph run                      # Start polling for jobs (foreground; wrap with launchd/systemd)
workgraph repo add <owner/name> <path>   # Map a local repo path (skips auto-clone)
workgraph repo list                # Show mapped repos
workgraph repo remove <owner/name> # Remove a repo mapping

Configuration

Credentials are stored at ~/.workgraph/config.json (mode 0600). The file contains your agent ID, bearer token, and the server URL you paired against. Delete with workgraph logout.

Environment variables:

| Variable | Effect | |--------------------------|----------------------------------------------------------------------| | WORKGRAPH_SERVER_URL | Default server URL for workgraph login (overridden by --url). | | WORKGRAPH_CONFIG_DIR | Override config + data dir (default ~/.workgraph). Useful for running a dev build alongside the globally-installed agent. |

Build from source

npm install
npm run build      # runs tsc → dist/
node dist/index.js run

Running the dev build alongside a globally-installed agent

Both binaries default to ~/.workgraph/config.json, so they would clash on credentials and repo mappings. Point the dev build at a separate directory with WORKGRAPH_CONFIG_DIR:

cd packages/agent

# One-time pairing against a local Next.js dev server (http://localhost:3000).
# `dev:login` already passes `--dev`, so it always pairs against localhost:
WORKGRAPH_CONFIG_DIR=~/.workgraph-dev npm run dev:login

# Run the dev agent (foreground) — uses the `dev` script which appends `run`:
WORKGRAPH_CONFIG_DIR=~/.workgraph-dev npm run dev

# Or, with auto-reload on source changes:
WORKGRAPH_CONFIG_DIR=~/.workgraph-dev npm run dev:watch

# Other subcommands have matching scripts:
WORKGRAPH_CONFIG_DIR=~/.workgraph-dev npm run dev:status
WORKGRAPH_CONFIG_DIR=~/.workgraph-dev npm run dev:logout
WORKGRAPH_CONFIG_DIR=~/.workgraph-dev npm run dev:repo -- list

The globally-installed workgraph binary keeps using ~/.workgraph as before — they do not see each other's config, repo maps, or auto-managed clones. Run them in separate terminals if you want both polling at once.

Test

npm test           # runs all *.test.ts via node:test

License

MIT — see LICENSE.