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

@evident-ai/cli

v0.2.0

Published

Evident CLI - Run OpenCode locally and connect to Evident

Readme

@connected/cli

Run OpenCode locally and connect it to the Connected platform.

Installation

npm install -g @connected/cli

Or run directly with npx:

npx @connected/cli <command>

Commands

connected login

Authenticate with Connected using your browser.

connected login

Options:

  • --no-browser - Don't open the browser automatically (copy the URL manually)
  • --token - Use token-based authentication (for CI/CD environments)

connected logout

Remove stored credentials from your machine.

connected logout

connected whoami

Show the currently authenticated user.

connected whoami

connected tunnel

Establish a tunnel from your local OpenCode instance to Connected.

connected tunnel

Options:

  • -s, --sandbox <id> - Connect to a specific sandbox ID
  • -p, --port <port> - OpenCode port (default: 4096)

Getting Started

1. Install and run OpenCode locally

First, install OpenCode and start it in your project directory:

# Install OpenCode
npm install -g @opencode/cli

# Start OpenCode server in your project
cd ~/projects/my-app
opencode serve --port 4096

2. Create a Local Mode sandbox

In the Connected web app (https://app.connected.run):

  1. Click "New Sandbox"
  2. Select "Local Mode"
  3. Click "Create Sandbox"

Note the sandbox ID from the URL or dashboard.

3. Connect via the CLI

# Authenticate (first time only)
connected login

# Start the tunnel
connected tunnel --sandbox <sandbox-id>

The tunnel will connect your local OpenCode to the Connected platform, enabling:

  • Chat through the web interface
  • WhatsApp and Slack integration
  • Session history and management

How It Works

+-------------------+     +-------------------+     +-------------------+
|  Your Machine     |     |  Cloudflare Edge  |     |  Connected API    |
|                   |     |                   |     |                   |
| OpenCode (4096) <-+---->| Tunnel Relay (DO) |<--->| Cloud Run         |
|                   |     |                   |     |                   |
| connected tunnel  |---->| WebSocket         |     | Neon DB           |
+-------------------+     +-------------------+     +-------------------+
  1. The CLI connects to OpenCode running on localhost
  2. Establishes a WebSocket connection to the tunnel relay
  3. Connected routes messages through the tunnel to your local OpenCode
  4. Responses flow back through the same path

Troubleshooting

"OpenCode not found on port 4096"

Make sure OpenCode is running:

opencode serve --port 4096

"Authentication failed"

Re-authenticate:

connected logout
connected login

"Tunnel disconnected"

The CLI will automatically reconnect. If issues persist:

  1. Check your internet connection
  2. Verify OpenCode is still running
  3. Try restarting the tunnel

Configuration

Credentials are stored in:

  • macOS/Linux: ~/.config/connected/
  • Windows: %APPDATA%\connected\

Environment variables:

  • CONNECTED_API_URL - Override the API URL (for development)
  • CONNECTED_TUNNEL_URL - Override the tunnel relay URL (for development)

Development

# Install dependencies
pnpm install

# Build
pnpm build

# Run locally
pnpm start <command>

# Type check
pnpm typecheck

License

MIT