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

@burtson-labs/agent-ui

v1.0.14

Published

UI primitives for the Bandit Agent Framework.

Downloads

583

Readme

@burtson-labs/agent-ui

UI primitives shared between the Bandit Stealth web app and the VS Code extension webview.

Host-agnostic React components — they consume a normalized event stream from the runtime and don't know whether they're rendering inside Vite, a VS Code webview, or the workbench harness.


Install

pnpm add @burtson-labs/agent-ui

Peer-depends on React 19, MUI 7, and emotion — the host app provides them. The runtime side (the event stream the components consume) comes from @burtson-labs/agent-core or the pre-wired @burtson-labs/stealth-core-runtime.

Quick start

Components are pure — they consume props and don't reach for any host. Import the CSS once at your app root, then drop components in:

import {
  MarkdownMessage,
  ChatComposer,
  ChatConversation,
  PlanTree,
  DiffStream,
  TelemetryPanel,
  AgentConsole
} from "@burtson-labs/agent-ui";
import "@burtson-labs/agent-ui/styles/agent-ui.css";

function ChatPanel({ messages, onSend }) {
  return (
    <>
      <ChatConversation messages={messages} />
      <ChatComposer onSubmit={onSend} placeholder="Type a message…" />
    </>
  );
}

What's in the box

| Component | What it renders | |---|---| | ChatComposer | Multi-line input + submit, with model picker, mode toggle, and skill chips | | ChatConversation | Streaming message list with assistant / user / tool / reasoning blocks | | MarkdownMessage | Single message bubble — markdown + syntax highlighting + file-reference links | | PlanTree | Plan + steps tree with progress states | | PlanActivity | Per-step activity feed (tool calls, diffs, logs) | | DiffStream | Live unified-diff viewer for proposed edits | | DiffReview/DiffReviewPanel | Multi-file accept / reject before applying | | TelemetryPanel | Token usage + per-iteration timing | | AgentConsole | Combined chat + plan + diff cockpit for the simple case | | PermissionCard | Inline allow/deny prompt for write-tool execution | | TaskList | Compact list of in-flight + recent agent runs | | BackgroundTaskTile | Live tile for a subagent the parent turn spawned |

Status

Stable. Used by the Bandit Stealth web app, the Bandit VS Code extension webview, and a mock-driven dev workbench. Breaking changes need a coordinated PR across the consumers.

Authoring a new component

Components live under src/components/. Each one should:

  1. Consume props only — no global state, no host-specific imports
  2. Be testable from a mock event-source harness
  3. Match the existing visual language (MUI primitives, dark/light theme aware)

License

Apache License 2.0 — Copyright 2026 Burtson Labs.