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

ai-sdk-relay-protocol

v0.2.0

Published

Wire protocol for an agent-session relay: provider-agnostic AgentEvent stream, session channel (client ⇄ relay ⇄ runner), replay cursors, and permission flow, all as Zod schemas.

Readme

ai-sdk-relay-protocol

The wire protocol for an agent-session relay: one Durable Object per session, many client sockets, exactly one runner driving the agent, and optionally one tool host serving local tools. Zod schemas are canonical; types are inferred so runtime validation and compile-time types never drift.

What it defines:

  • AgentEvent: the provider-agnostic output stream a runner emits (turn, text, reasoning, tool, artifact, error). Runners map harness stream parts (@ai-sdk/harness-*) onto these; provider-specific shapes never reach the relay or clients.
  • Session channel: the frame unions for each connection, ClientToSession, RunnerToSession, SessionToClient (sequenced updates, replay cursors, live text chunks, permission lifecycle), SessionToRunner, and the tool-host pair HostToSession / SessionToHost.
  • Permission lifecycle: requests, decisions, and a sequenced resolution for every request (answered, replayed, withdrawn, superseded, or unavailable).
  • Turn receipts and archives: TurnReceipt records a prompt's acceptance and progress; SessionArchive is a session's total state as one portable document, for moves and forks.
  • toModelMessages and archiveEvents: toModelMessages rehydrates a replay log into AI SDK ModelMessages, so the log is the canonical conversation state and a session can resume or hand off on any provider. archiveEvents extracts the events from an exported archive, so toModelMessages(archiveEvents(archive)) rebuilds a moved session's conversation.
  • decode / encode: malformed or oversized frames become typed errors, never exceptions or any.

The reference relay is ai-sdk-relay; the tool-host client is ai-sdk-relay-host. The reference product is dispatch, where this protocol was extracted from.