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

@tangle-network/agent-ui

v0.2.0

Published

Shared agent UI components and sidecar integration hooks for Tangle blueprints

Readme

@tangle-network/agent-ui

Shared agent-facing UI package for Tangle apps.

Scope

Put code in @tangle-network/agent-ui when it is:

  • Agent chat/session UX (ChatContainer, run timeline, tool previews)
  • Agent markdown rendering and tool/result presentation
  • Sidecar auth/session orchestration and PTY terminal integration
  • Reusable agent-focused primitives/hooks (@tangle-network/agent-ui/primitives)

Do not put code here when it is:

  • Chain/contract/provisioning infra (belongs in @tangle-network/blueprint-ui)
  • Product-specific route composition, copy, or business workflows (belongs in the app)
  • Sandbox-only shell/layout styling concerns (belongs in the sandbox app)

Public API

Entrypoints:

  • @tangle-network/agent-ui: main agent components/hooks/types
  • @tangle-network/agent-ui/primitives: small shared helpers/hooks for consumer UIs
  • @tangle-network/agent-ui/terminal: lazy terminal view entry
  • @tangle-network/agent-ui/styles: package stylesheet

Treat exported symbols as stable contract; prefer additive changes over breaking renames/removals.

Usage

import { ChatContainer, useWagmiSidecarAuth } from '@tangle-network/agent-ui';
import { copyText, timeAgo } from '@tangle-network/agent-ui/primitives';

const TerminalView = React.lazy(() =>
  import('@tangle-network/agent-ui/terminal').then((m) => ({ default: m.TerminalView })),
);

Extraction Rule

If Sandbox and Arena share substantial agent-facing code (roughly 20+ lines), extract it here instead of duplicating app-local logic.

Release

  • Publish target: npm package @tangle-network/agent-ui
  • Workflow: .github/workflows/publish-agent-ui.yml
  • Tag format: agent-ui-vX.Y.Z (must match packages/agent-ui/package.json version)

Repo Strategy

@tangle-network/agent-ui is a cross-product package for shared agent experience building blocks.

Keep it in this repo while:

  1. Most API changes are driven by sandbox-runtime sidecar integration work.
  2. Release cadence matches this monorepo.

Split to its own repo when:

  1. There are 3+ external consumers with independent release cadence.
  2. Separate ownership/review boundaries are needed.
  3. Most changes no longer depend on this monorepo internals.

Consumer Checklist

Before merging changes that touch agent UX:

  1. Check if the same pattern exists in both UIs.
  2. If yes and app-agnostic, move it into @tangle-network/agent-ui.
  3. Keep exports explicit in src/index.ts or src/primitives.ts.
  4. Verify both consumers still typecheck/build after the change.