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

@threadbase-sh/agent-types

v1.0.0

Published

Shared wire types for the Threadbase multi-agent pipeline (tb-multi-agent ↔ tb-streamer).

Downloads

1,718

Readme

@threadbase/agent-types

Shared wire types for the Threadbase multi-agent pipeline.

These types live on the boundary between two processes:

  • tb-multi-agent — the Temporal worker that runs the orchestrator + turn workflows and the AI-agent activities.
  • tb-streamer — the Temporal client that owns the WebSocket connection to the mobile frontend and writes JSONL.

Both processes consume this package so the wire shapes (progress events, signal payloads, session addendum, final-answer flags) stay in sync. There is no runtime code beyond a single frozen STAGES array; everything else is type-only.

How consumers depend on this

Both consumers add this repo as a git submodule at a pinned commit, then point their package.json at the submodule path via a file: dep:

// tb-multi-agent/packages/agent-types/  ← submodule path
// tb-streamer/vendor/agent-types/       ← submodule path

"@threadbase/agent-types": "file:packages/agent-types"  // tb-multi-agent
"@threadbase/agent-types": "file:vendor/agent-types"    // tb-streamer

Bumping the wire contract is a deliberate three-step act:

  1. Edit + commit + push here.
  2. In the consuming repo, git submodule update --remote vendor/agent-types (or packages/agent-types).
  3. Commit the submodule SHA bump in the consuming repo.

This pattern mirrors how tb-streamer consumes @threadbase/scanner today.

Why private: true in package.json

The package is source-public (this repo is public on GitHub) but not published to npm. The private: true flag prevents accidental npm publish runs. The roadmap for going registry-public lives alongside the tb-streamer distribution refactor — both packages move to npm together (Stage 3 in tb-multi-agent/docs/ROADMAP.md).

Stages of distribution maturity

  • ~~Stage 1: local file: dep, sibling-checkout requirement.~~ Retired 2026-06-04.
  • Stage 2 (current): standalone GitHub repo, consumed via git submodule. Both consumers pin a SHA.
  • Stage 3 (planned): published npm package. See tb-multi-agent/docs/ROADMAP.md and the tb-streamer distribution-refactor spec for the broader unification.

Local development

npm install
npm test       # vitest, 23 tests
npm run build  # tsc → dist/
npm run typecheck

The package is self-contained: no runtime deps, only typescript + vitest as devDeps.