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

@preloop-ai/claude-plugin

v0.1.1

Published

See your live Claude Code sessions from the Preloop console or your phone, send them a turn, and interrupt them from anywhere. Prototype.

Readme

Reach your Claude Code sessions from anywhere

A Claude Code session you started this morning is still running. You are not at that keyboard, and there is no way to see it or say anything to it.

@preloop-ai/claude-plugin is the Preloop Agent Control sidecar for Claude Code. It connects Claude Code to Preloop, the open-source AI agent control plane, so that:

  • You can see which sessions are alive, from the Preloop console and the mobile apps.
  • You can talk to them. Send a message into a sidecar-owned session, resume a persisted one by id, or interrupt the current turn. Operator text lands as an auditable user turn, never a hidden system prompt.
  • Approvals keep working without it. Tool approvals stay on the Claude Code hook path, so stopping the sidecar never leaves anything ungoverned.

It uses the same preloop.agent_control.v1 protocol as the Hermes and OpenClaw runtime plugins. Apache-2.0.

Status: prototype (issue preloop/preloop#131). Read Honest limitations before you rely on it.

Why a sidecar

Hermes and OpenClaw load Preloop's plugin in-process. Claude Code has no equivalent in-process extension API for message injection: its extension surface is hooks (child processes) and the Agent SDK (be the host process). So this package runs as a long-lived sidecar daemon that owns the Agent Control WebSocket and drives Claude Code through the Claude Agent SDK.

What it does

  • Owned sessions (full steering). Operator messages from the Preloop console/mobile start a new Claude Code session, or are pushed into a live sidecar-owned session via SDK streaming input, or resume a persisted session by id. interrupt stops the current turn. Operator text is an auditable user turn, never a hidden system prompt.
  • Observed sessions (presence + approvals). Interactive terminal sessions cannot receive injected turns; the sidecar tails ~/.claude/projects/**/*.jsonl and reports presence/telemetry as session_activity events. Targeting a persisted-but-idle session resumes it headlessly. Summaries only; transcripts are not uploaded.
  • Approvals stay on the hook path. Tool approvals are handled by the PreToolUse hook installed by preloop agents onboard "Claude Code" --approvals. The sidecar advertises tool_approval but never reimplements it, so stopping the sidecar never ungoverns anything (fail-closed posture preserved). Setting sources are loaded for owned sessions so the same hook fires there too.

Honest limitations

  • A live interactive TUI session cannot be steered mid-turn. You get observe + approve; steering requires the session to be owned or resumed by the sidecar once idle.
  • interrupt on an observed TUI session fails with a clear error rather than sending signals to a terminal someone is typing into.

Configuration

The sidecar reads ~/.claude/preloop-control.json (its own file; ~/.claude/settings.json stays reserved for Claude Code's own schema). preloop agents onboard "Claude Code" writes the settings nested under a top-level "control" key; a flat file (all keys at the top level) is accepted too. A file with neither shape yields no usable settings and the sidecar logs a loud warning instead of idling silently.

{
  "control": {
    "enabled": true,
    "protocol": "preloop.agent_control.v1",
    "runtime": "claude_code",
    "control_ws_url": "wss://app.preloop.ai/api/v1/agents/control/ws",
    "bearer_token": "agt_...",
    "managed_agent_id": "...",
    "runtime_principal_id": "claude-code-...",
    "runtime_principal_name": "Claude Code",
    "workspace_root": "/path/to/default/workspace"
  }
}

Optional keys: permission_mode, transcript_dir, observer_enabled, observer_poll_ms, turn_timeout_ms (per-turn reply timeout, default 5 minutes; a hung turn is rejected so the sidecar keeps serving commands).

Usage

npm install -g @preloop-ai/claude-plugin
preloop-claude-plugin verify            # check the config
preloop-claude-plugin run               # start the sidecar
preloop-claude-plugin run --config /path/to/preloop-control.json

Development

npm install
npm run build
npm test

Tests use Node's built-in test runner with a fake Agent SDK; no network or Claude Code install is required.