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

@teamvibe/poller

v0.1.50

Published

Self-hosted poller that connects your Slack workspace to Claude Code via TeamVibe.

Downloads

5,040

Readme

@teamvibe/poller

Self-hosted poller that connects your Slack workspace to Claude Code via TeamVibe.

Prerequisites

  • Node.js 20+
  • Claude Code CLI (claude) installed and authenticated
  • A TeamVibe poller token (get one from the TeamVibe dashboard)

Quick Start

Install as a macOS service (recommended)

npx @teamvibe/poller install

The interactive installer will:

  1. Prompt for your TEAMVIBE_POLLER_TOKEN
  2. Prompt for your CLAUDE_CODE_OAUTH_TOKEN (or auto-detect it)
  3. Configure optional settings (API URL, max concurrent sessions)
  4. Detect your claude CLI path
  5. Install the package globally (if needed) for a stable service path
  6. Create ~/.teamvibe/.env with your configuration
  7. Install and start a launchd service that runs automatically on login

Run directly

npx @teamvibe/poller

Make sure ~/.teamvibe/.env exists with at least TEAMVIBE_POLLER_TOKEN set.

Updating

npx @teamvibe/poller update

This updates the global installation to the latest version and restarts the service if installed.

Service Management

poller status     # Check if the service is running
poller stop       # Stop the service
poller start      # Start the service
poller restart    # Restart the service
poller uninstall  # Remove the service

Logs

When running as a service, logs are written to:

~/.teamvibe/logs/poller.stdout.log
~/.teamvibe/logs/poller.stderr.log

Follow logs in real-time:

tail -f ~/.teamvibe/logs/poller.stdout.log

Configuration

All configuration is via environment variables (or ~/.teamvibe/.env):

| Variable | Required | Default | Description | |----------|----------|---------|-------------| | TEAMVIBE_POLLER_TOKEN | Yes | — | Your poller authentication token | | CLAUDE_CODE_OAUTH_TOKEN | No | — | Claude Code OAuth token (from claude setup-token) | | TEAMVIBE_API_URL | No | https://poller.api.teamvibe.ai | API endpoint | | MAX_CONCURRENT_SESSIONS | No | 5 | Max parallel Claude sessions | | CLAUDE_CLI_PATH | No | claude | Path to Claude Code CLI | | TEAMVIBE_DATA_DIR | No | ~/.teamvibe | Data directory for brains and state |

How It Works

The poller authenticates with the TeamVibe API using your token, then continuously polls an SQS queue for incoming messages from Slack. When a message arrives, it spawns a Claude Code session with the appropriate brain (knowledge base) and streams the response back to Slack.