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

@tclawio/bridge

v0.3.3

Published

Local daemon that bridges OpenClaw instances to Teleclaw cloud service

Readme

tclaw-bridge

Local daemon that bridges your OpenClaw instance to the Teleclaw cloud service.

What it does

  • Connects your local OpenClaw (localhost) to Teleclaw without exposing ports
  • Outbound WebSocket connection (works through firewalls/NAT)
  • Handles commands from Teleclaw Mini App
  • Sends status updates and logs to Teleclaw
  • Auto-reconnects if connection drops

Installation & Usage

Quick Start

npx tclaw-bridge \
  --user-id YOUR_TELEGRAM_ID \
  --token YOUR_CONNECTION_TOKEN

Environment Variables

Instead of passing flags, you can set:

export OPENCLAW_URL=http://localhost:18789
export OPENCLAW_TOKEN=your-openclaw-gateway-token
export TELECLAW_SERVER=wss://api.teleclaw.io

Then just run:

npx tclaw-bridge --user-id 123456 --token abc...

Full Options

npx tclaw-bridge \
  --user-id 123456789 \
  --token abc123...xyz \
  --server wss://api.teleclaw.io \
  --openclaw-url http://localhost:18789 \
  --openclaw-token your-token

How It Works

┌──────────────┐     ┌──────────────┐     ┌──────────────┐
│  OpenClaw    │ ←── │ tclaw-bridge │ ──→ │  Teleclaw    │
│  (localhost) │     │   (local)    │     │   (cloud)    │
└──────────────┘     └──────────────┘     └──────────────┘
  1. Bridge polls OpenClaw locally (every 30s)
  2. Bridge connects OUTBOUND to Teleclaw WebSocket server
  3. Teleclaw sends commands → Bridge → OpenClaw
  4. OpenClaw responses → Bridge → Teleclaw → Your Mini App

Security

  • ✅ No inbound ports opened (outbound-only connection)
  • ✅ TLS encrypted (wss://)
  • ✅ Token-based authentication
  • ✅ OpenClaw gateway never exposed to internet

Requirements

  • Node.js 18+ (LTS recommended)
  • OpenClaw running locally
  • OpenClaw gateway token

Troubleshooting

"OpenClaw unreachable"

Check if OpenClaw is running:

openclaw status

Make sure gateway is on port 18789 (default) or set OPENCLAW_URL to the correct port.

"Connection refused"

Check your internet connection and firewall. The bridge needs outbound WebSocket (wss://) access.

"Unauthorized"

Your Teleclaw connection token may be invalid. Get a new one from the Teleclaw Mini App → Settings → Connections.

License

MIT