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

clawdot

v0.3.0

Published

Run coding agents on your machine, drive them from your phone — terminal sessions over an end-to-end encrypted relay

Downloads

437

Readme

clawdot

Run coding agents (claude, codex, …) in terminal sessions on your own machine and drive them from your phone. The daemon hosts the terminals; your phone connects through a relay you host, end-to-end encrypted — the relay only ever sees ciphertext.

Install

npm install -g clawdot
clawdot          # interactive menu — the first run opens the setup wizard

The wizard configures the relay and port, detects your platform, and offers to install the daemon as a background service that starts at login and restarts after crashes:

| Platform | Mechanism | | -------- | --------- | | macOS | launchd LaunchAgent | | Linux | systemd user unit (needs a systemd user manager — the wizard tells you if there is none, e.g. in WSL or containers) | | Windows | Startup-folder launcher (no admin rights needed) |

No background service available? clawdot serve runs the daemon in the foreground anywhere Node 20+ runs.

Linux note: the bundled PTY binaries are prebuilt for glibc — Alpine/musl is not supported.

Commands

clawdot setup              # guided configuration (relay, port, background service)
clawdot service install    # install/update the background service
clawdot pair               # QR-pair a phone through your relay
clawdot devices            # list / revoke paired devices
clawdot config             # change settings later
clawdot serve              # run the daemon in the foreground

Remote access

There is no default relay and nothing phones home: you deploy the relay container yourself and point the daemon at it (the wizard, or clawdot --relay wss://your-domain/v1). Pairing uses a one-time QR ticket; afterwards each device's own key is its credential. See the project repository for the relay Dockerfile and full documentation.