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

claude-artifacts-chat-server

v1.4.0

Published

Local WebSocket server for context-aware AI chat on documentation sites

Downloads

307

Readme

Claude Artifacts Chat Server

Local WebSocket server that enables context-aware AI chat on the docs site.

Quick Start

npm install
npm start

Server runs on ws://localhost:8765

Press Ctrl+C to stop.

How It Works

  • Proxies your local Claude Code instance
  • Uses YOUR credentials (Slack, GitHub, etc.)
  • All processing happens locally
  • No data sent to external services

What Gets Shared

When you ask a question in the chat widget:

  • The current document title and content (first ~8k characters)
  • Your question
  • These are sent to your LOCAL Claude Code instance only

Claude Code can then use your configured MCP tools (Slack, GitHub, Linear, etc.) to find additional context if needed.

Security

  • Everything runs locally on your machine
  • Uses your existing Claude Code authentication
  • No data leaves your computer except through your own MCP tools
  • Server only listens on localhost (not accessible from network)

Permission Mode

The server runs Claude with --dangerously-skip-permissions to enable MCP tool usage in headless mode. This means:

  • ✅ Claude can use your MCP tools (Slack, Linear, GitHub, etc.) without prompting
  • ✅ Faster responses - no permission dialogs
  • ⚠️ Claude will execute tool calls automatically based on the document context and your questions
  • ⚠️ Only run this server when you trust the documents you're viewing

This is safe because:

  • You control what questions are asked
  • Tool usage is logged in the server console
  • All tools use your own credentials and permissions
  • The server only processes requests from localhost

Troubleshooting

"Failed to communicate with Claude Code"

Make sure Claude Code CLI is installed and in your PATH:

which claude

If not found, install Claude Code from https://claude.com/claude-code

"There's an issue with the selected model"

Your Claude Code default model might not exist or you don't have access to it.

Check available models:

claude --model

Common valid models:

  • claude-opus-4
  • claude-sonnet-4
  • claude-haiku-4

To change your default model, update your Claude Code settings or use the model selector in the Claude Code UI.

Port already in use

If you see "Address already in use", another process is using port 8765:

# Find and stop the process
lsof -ti:8765 | xargs kill -9

Chat widget shows "offline"

  1. Check that the server is running: look for "🚀 Chat server running" message
  2. Check browser console for WebSocket errors
  3. Try refreshing the page