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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@absmartly/claude-code-bridge

v1.0.2

Published

HTTP bridge server for ABsmartly Extension to communicate with Claude Code CLI

Vulnerabilities

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

Links

Git

Maintainers

marcioapmmarcioapmjoalvesjoalvescaltheabtestercaltheabtestermarcioabsmarcioabs

Keywords

claudeabsmartlyab-testingbridge

Readme

@absmartly/claude-code-bridge

HTTP bridge server that enables the ABsmartly Browser Extension to communicate with Claude Code CLI for AI-powered A/B testing features.

Prerequisites

  • Node.js 16+
  • Claude Code CLI authenticated: npx @anthropic-ai/claude-code login

Quick Start

npx @absmartly/claude-code-bridge

The server will start on http://localhost:3000 by default.

Usage

1. Login to Claude CLI (one-time setup)

npx @anthropic-ai/claude-code login

Follow the prompts to authenticate with your Claude subscription.

2. Start the bridge server

npx @absmartly/claude-code-bridge

3. Configure ABsmartly Extension

In the extension settings:

  1. Select "Claude Subscription" as your AI provider
  2. The extension will automatically connect to http://localhost:3000

Custom Port

PORT=3001 npx @absmartly/claude-code-bridge

API Endpoints

  • GET /health - Health check and auth status
  • GET /auth/status - Claude CLI authentication status
  • POST /conversations - Create new conversation
  • POST /conversations/:id/messages - Send message to Claude
  • GET /conversations/:id/stream - Stream Claude responses (SSE)
  • POST /conversations/:id/approve - Approve tool use
  • POST /conversations/:id/deny - Deny tool use

How It Works

  1. Authentication Check: Reads your Claude credentials from ~/.claude/.credentials.json
  2. Claude CLI Spawn: Spawns npx @anthropic-ai/claude-code --json subprocess
  3. HTTP Bridge: Provides REST API for the browser extension to communicate
  4. Message Forwarding: Routes messages between the extension and Claude CLI
  5. Server-Sent Events: Streams Claude responses back to the extension in real-time

Troubleshooting

"Claude CLI not logged in"

Run: npx @anthropic-ai/claude-code login

"Port already in use"

Either:

  • Kill the existing process: pkill -f claude-code-bridge
  • Or use a different port: PORT=3001 npx @absmartly/claude-code-bridge

Extension can't connect

  • Ensure the bridge is running: http://localhost:3000/health should return JSON
  • Check the port matches in extension settings
  • Restart the extension

License

MIT