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

@chassdev/agent-tunnel

v0.1.0

Published

Tunnel relay between cloud AI agents and local machines — server relay, local agent, client SDK, JSON-RPC, HMAC signing

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

pierrebalderapierrebaldera

Keywords

tunnelrelaywebsocketjson-rpchmacagentsdk

Readme

@chassdev/agent-tunnel

@chassdev/agent-tunnel connects a local computer to Chass through an authenticated reverse tunnel.

Connect once

Run the command shown in a Computer Tunnel connector profile. Then approve the device code in your browser:

npx --yes @chassdev/agent-tunnel@latest connect \
  --api-url https://api.chass.app/v1/tunnel

After approval, the interactive flow asks whether it should install a persistent background service. The default answer is yes.

Run in the background

Install the operating-system background service during connection:

npx --yes @chassdev/agent-tunnel@latest connect \
  --daemon \
  --api-url https://api.chass.app/v1/tunnel

The service uses LaunchAgent on macOS, a user systemd service on Linux, and Task Scheduler on Windows. It starts at login and restarts after failures. It does not change the computer's sleep settings.

Manage the background service

npx --yes @chassdev/agent-tunnel@latest service-status
npx --yes @chassdev/agent-tunnel@latest logs
npx --yes @chassdev/agent-tunnel@latest restart
npx --yes @chassdev/agent-tunnel@latest stop
npx --yes @chassdev/agent-tunnel@latest uninstall-service

Credentials are stored in ~/.agent-tunnel/config.json. Agent Tunnel requires the file to be regular, owned by the current user, and mode 0600 on POSIX. Protect the operating-system account because this setup token can authenticate the machine until you rotate or delete the connection.

Remote API URLs must use HTTPS. Plain HTTP is accepted only for localhost, 127.0.0.1, and ::1 development endpoints.

Permission boundaries

Chass checks connector profile assignment, connector grants, connector tool policy, and the machine permission before relaying an operation. The local agent then checks the machine permission again.

The local config is the maximum boundary. A server grant cannot widen configured filesystem paths, blocked paths, shell commands, timeouts, file sizes, or desktop features. An empty permission scope is unrestricted inside those local ceilings. Use scoped permissions and short expiries for sensitive machines.

Computer Use driver

Agent Tunnel never downloads or executes a desktop driver. Install cua-driver locally before enabling Computer Use. The tunnel uses an existing binary from CUA_DRIVER_BIN, ~/.local/bin, /usr/local/bin, or /opt/homebrew/bin. Treat that binary as trusted local code. Agent Tunnel does not verify or update it.