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

@ai-development-environment/control-agent

v0.0.93

Published

Control agent for the AI Development Environment

Readme

@ai-development-environment/control-agent

Control agent for the AI Development Environment. It makes authenticated outbound HTTP and GraphQL WebSocket connections to the control plane; managed machines do not expose a listening port.

Install

npm install -g @ai-development-environment/control-agent

Requires Node.js 24 (>=24.16.0 <25). Saved commands use the agent user's login shell and require no additional runtime.

Usage

Open the server's Agents page and create a one-time enrollment command, then run it on the target machine (the server defaults to the same computer when omitted):

control-agent enroll \
  --server http://127.0.0.1:3090 \
  --enrollment-token <one-time-token>
control-agent run

Local and remote endpoints

One control plane is often reachable at two addresses — a LAN address at the desk and a public or VPN address elsewhere. Configure both and the agent prefers the local one, moving to the remote one when the local address stops answering and the remote one is confirmed to be answering. A control plane that is down at every configured address is not a failover: the agent keeps its session and the jobs running under it, and reconnects when the server comes back.

control-agent enroll \
  --server http://192.168.1.10:3090 \
  --remote-server https://control.example.com \
  --enrollment-token <one-time-token>

Change the addresses on an enrolled agent, or print the current ones by passing no flags:

control-agent endpoints
control-agent endpoints --remote-server https://control.example.com
control-agent endpoints --clear-remote

The websocket address of each endpoint is derived from its server URL unless --websocket-server or --remote-websocket-server sets it explicitly.

Changing a server address re-derives its websocket address, because one stored against the old server no longer points anywhere useful. If the websocket is served from somewhere other than /graphql on the same host and port — behind a reverse proxy, say — pass it alongside the new server address:

control-agent endpoints --server http://192.168.1.20:3090 --websocket-server ws://192.168.1.20:3092/graphql

Enrollment

control-agent enrollment
control-agent unenroll

enrollment reports whether this machine is enrolled and whether each configured endpoint answers for it. unenroll removes the local credential; the control plane still lists the agent until it is deleted there.

Diagnostics:

control-agent status
control-agent doctor

The credential and stable agent ID are stored at ~/.config/control-agent/config.json.

See also