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

@zclaudia/protocol

v0.3.0

Published

ZClaudia business contracts: resources, sync payloads, notification semantics, and transport binding conventions.

Vulnerabilities

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

Links

Git

Maintainers

zhvalazhvala

Keywords

Readme

@zclaudia/protocol

ZClaudia business contracts shared across desktop, server, and SDKs: business resource models, sync payloads, notification semantics, and this application's transport binding conventions. Gateway transport contracts (handshake, control plane, channels, topics, HTTP frames) live in the independent @zclaudia/gateway-protocol package — the two protocol packages do not depend on each other.

Entries

  • @zclaudia/protocol — everything below re-exported.
  • @zclaudia/protocol/zclaudia — business models (SessionItem, ProjectItem, SessionMessage, RunStatus).
  • @zclaudia/protocol/sync — business sync payloads published over gateway topics/channels (backend_resource_snapshot, backend_resource_event, catch_up_content, content_patch, content_patch_error).
  • @zclaudia/protocol/transport — ZClaudia binding conventions: namespace, resources topic, zclaudia channel kind.
  • @zclaudia/protocol/notifications — application notification event semantics and user-facing config shape.
  • @zclaudia/protocol/core — opaque payload and envelope primitives.

Migration notes for 0.3.0

The frozen compatibility entries removed in 0.3.0, and where their content lives now:

  • @zclaudia/protocol/gateway — gateway transport contracts moved to @zclaudia/gateway-protocol (protocol v4). The dead v3 wire names (subscribe_backend, http_proxy_*, stream demand, the legacy HTTP proxy frames, …) have no replacement: the v4 gateway never routed them.
  • @zclaudia/protocol/agent — the legacy agent runtime contracts had no consumers; runtime interaction contracts live in plugin-sdk. The run status set survives unchanged as RunStatus in /zclaudia.

Install

npm install @zclaudia/protocol

Usage

import type { SessionItem } from '@zclaudia/protocol/zclaudia';
import type { BackendResourceEventMessage } from '@zclaudia/protocol/sync';
import { RESOURCES_TOPIC, MESSAGE_CHANNEL_KIND } from '@zclaudia/protocol/transport';

License

MIT