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

@contextableai/clawpilotkit

v0.1.0

Published

CopilotKit-based UI for OpenClaw — embeds into the operator console chat.surface slot and also runs standalone against a clawg-ui gateway

Vulnerabilities

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

Links

Git

Maintainers

contextablemarkcontextablemark

Keywords

openclawclawg-uicopilotkitag-uichatslot

Readme

@contextableai/clawpilotkit

CopilotKit-based chat UI for clawg-ui.

The same prebuilt React + CopilotKit bundle runs in two modes:

  • Embedded — as an OpenClaw plugin contributing the chat.surface slot in the operator console. The host iframe sends a context payload over postMessage (gateway URL, operator token, current session); the bundle wires CopilotKit straight to the clawg-ui operator-auth AG-UI route.
  • Standalone — served by a tiny launcher against any clawg-ui gateway. The bundle falls into a setup screen, walks the user through device pairing, and then runs CopilotKit against the gateway's pairing-auth AG-UI route.

The bundle picks its mode at runtime: it pings its parent window with openclaw:ready and waits ~500 ms for a context message; if none arrives it switches to standalone.

Embedded (OpenClaw plugin)

openclaw plugins install @contextableai/clawpilotkit

Restart the gateway. The plugin auto-registers the static UI route (/v1/clawpilotkit/ui) and contributes the chat.surface slot, so the operator console's Chat tab embeds the CopilotKit UI in place of the built-in message thread + input box. No further configuration required; authentication piggy-backs on the operator token the host already holds.

Standalone (CLI launcher)

npx @contextableai/clawpilotkit
# → [clawpilotkit] open http://127.0.0.1:3939/

Open the printed URL in a browser. The setup screen accepts a clawg-ui gateway URL (e.g. http://localhost:18789); on submit it kicks off the device-pairing flow against /v1/clawg-ui on that gateway. Once the gateway owner approves the pairing (openclaw pairing approve clawg-ui <code>), CopilotKit chat goes live against the gateway.

Flags:

--port, -p    port to bind (default 3939, env PORT)
--host, -h    host to bind (default 127.0.0.1, env HOST)
--help        show usage

The gateway must be running clawg-ui ≥ 0.7 so the pairing route allows cross-origin requests from the launcher's origin.

Building

npm install
npm run build      # builds the React app into ui/ and the plugin entry into dist/
npm run dev:app    # vite dev server for the React app (no auto plugin install)

npm run build:app writes the bundle to ui/. The launcher in bin/ serves that directory as-is and the plugin's static handler maps it under /v1/clawpilotkit/ui/ when running in embedded mode.