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

agentknight

v0.9.6

Published

AgentKnight PC Agent CLI for remote GitHub Copilot sessions

Readme

AgentKnight

AgentKnight PC Agent connects local GitHub Copilot sessions to an AgentKnight Relay Server.

Run

Node.js 20.19.0 or newer and an authenticated GitHub Copilot CLI are required.

npx agentknight --env C:\path\to\agentknight.env

Or install it globally:

npm install --global agentknight
agentknight --env C:\path\to\agentknight.env

Without --env, AgentKnight reads .env from the current directory.

Configuration

RELAY_URL=https://your-relay-host
RELAY_TOKEN=replace-with-your-relay-token
USER_ID=admin
AGENTKNIGHT_MACHINE_NAME=optional-custom-pc-name
COPILOT_REMOTE_HOME=C:\optional\isolated\instance-data
SESSION_REFRESH_INTERVAL_MS=30000
HEARTBEAT_INTERVAL_MS=15000
LOG_LEVEL=info
SHOW_PAIRING_QR=true
PAIRING_PAGE_ENABLED=true
PAIRING_PAGE_PORT=17888

RELAY_URL is used for HTTP APIs and Socket.IO, so an https:// URL enables HTTPS and WSS for the entire PC Agent connection. Use a distinct COPILOT_REMOTE_HOME for each concurrently running instance so each one has a unique machine identity. AGENTKNIGHT_MACHINE_NAME controls the PC name shown to mobile clients, and PAIRING_PAGE_PORT allows concurrent instances to avoid the default 17888 port.

Relays with a certificate issued by a publicly trusted CA work without extra configuration. For a private or self-signed Relay CA on Windows, keep the public CA certificate at a stable local path, such as $env:OneDrive\AgentKnight\certificates\agentknight-ca.crt, and configure it before starting Node:

$caPath = "$env:OneDrive\AgentKnight\certificates\agentknight-ca.crt"
[Environment]::SetEnvironmentVariable("NODE_EXTRA_CA_CERTS", $caPath, "User")
$env:NODE_EXTRA_CA_CERTS = $caPath
npx agentknight --env C:\path\to\agentknight.env

Restart existing terminals after setting the user environment variable. Mark the OneDrive certificate Always keep on this device on every PC. Node reads NODE_EXTRA_CA_CERTS only when the process starts, so do not put it only in the AgentKnight --env file. The file must contain PEM-encoded public CA certificates only, never a private key.

Repository checkouts also include Windows Scheduled Task and macOS LaunchAgent installers under client/pc/scripts. Pass the CA path when installing the service so every background restart sets NODE_EXTRA_CA_CERTS before Node starts. On Windows, build the path from $env:OneDrive rather than hard-coding a user-specific absolute path.

Keep RELAY_TOKEN in the environment file. Do not pass it as a command-line argument or commit it to source control.

See the AgentKnight repository for Relay Server and Android client setup.