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

@copilotkit/bot-ui

v0.0.3

Published

JSX runtime, IR, and cross-platform component vocabulary for CopilotKit bots.

Readme

@copilotkit/bot-ui

A pure JSX runtime + intermediate representation (IR) + cross-platform component vocabulary for authoring rich bot messages. No React, no agent runtime, no Slack — @copilotkit/bot-ui depends on nothing in the repo except @copilotkit/shared (for StandardSchemaV1 types). That's what lets a platform adapter (e.g. @copilotkit/bot-slack) translate the same UI into Block Kit, while keeping the component layer tree-shakeable and testable in isolation.

You author UI as JSX, it normalizes to one serializable IR (BotNode[]), and behavior props (onClick / onSelect / onSubmit) ride along on the nodes for the engine (@copilotkit/bot) to bind.

Install

pnpm add @copilotkit/bot-ui

To author components as JSX, point the TypeScript JSX factory at this package in the consuming project's tsconfig.json:

{
  "compilerOptions": {
    "jsx": "react-jsx",
    "jsxImportSource": "@copilotkit/bot-ui",
  },
}

This package ships @copilotkit/bot-ui/jsx-runtime (and /jsx-dev-runtime) exporting jsx / jsxs / Fragment. Author component files as .tsx.

Example

import {
  Message,
  Header,
  Section,
  Actions,
  Button,
  renderToIR,
} from "@copilotkit/bot-ui";

function Greeting({ name }: { name: string }) {
  return (
    <Message>
      <Header>Hello {name}</Header>
      <Section>Pick an option — **bold** and `code` work too.</Section>
      <Actions>
        <Button
          style="primary"
          onClick={(ctx) => ctx.thread.post("you clicked!")}
        >
          Continue
        </Button>
      </Actions>
    </Message>
  );
}

const ir = renderToIR(<Greeting name="Ada" />);
// ir is BotNode[] — hand it to an adapter, or let @copilotkit/bot post it.

renderToIR(ui: Renderable): BotNode[] recursively invokes any component function (passing its props) until only intrinsic string-typed nodes remain; strings in children become { type: "text", props: { value } }; Fragment flattens its children. Components must be pure functions of serializable props — same props in, same tree out — which is what makes content-stable action binding and re-render rehydration possible in @copilotkit/bot.

Renderable also accepts a { raw } escape hatch, which renderToIR passes through as { type: "raw", props: { value } } for adapters that want to short-circuit to a native payload.

Component vocabulary

Each component is a thin function returning a BotNode with a stable intrinsic type string. An adapter maps these to native primitives.

Every component has a fully-typed prop interface (MessageProps, ButtonProps, …, all exported), and the package ships its own JSX namespace (resolved via jsxImportSource: "@copilotkit/bot-ui"). So JSX is statically checked: unknown attributes, wrong prop values, and bad children are compile-time errors — <Section bogus={1} /> or <Button style="nope"> won't type-check. There are no lowercase intrinsic tags; the vocabulary is the capitalized component set below.

| Component | Purpose | | ---------- | ----------------------------------------------------------------- | ---------- | | Message | Root container for a single posted message. | | Header | Bold header / title row. | | Section | A block of (markdown) body text. | | Markdown | Explicit markdown text block. | | Field | One label/value cell inside Fields. | | Fields | A grid of Fields (two-column key/value layout). | | Context | Small, muted secondary text (footnotes, metadata). | | Actions | Row container for interactive controls. | | Button | Clickable button — onClick, value, style: "primary" | "danger". | | Select | Dropdown — onSelect, placeholder, options: {label,value}[]. | | Input | Text input — onSubmit, placeholder, multiline, name. | | Image | An image block. | | Divider | A horizontal rule. |

Behavior props

Interactive components carry handler props typed as ClickHandler:

  • ButtononClick
  • SelectonSelect
  • InputonSubmit

A ClickHandler receives an InteractionContext, both generic over the clicked control's value type:

type ClickHandler<TValue = unknown> = (
  ctx: InteractionContext<TValue>,
) => void | Promise<void>;

interface InteractionContext<TValue = unknown> {
  thread: Thread;
  message: IncomingMessage;
  action: { id: string; value?: TValue };
  values: Record<string, unknown>;
  user: PlatformUser;
  platform: string;
}

Button is generic over its value prop, so ctx.action.value is inferred from value<Button value={{ confirmed: true }} onClick={(ctx) => ctx.action.value?.confirmed}> type-checks with no cast. Select/Input resolve the value to string.

The structural types Thread, IncomingMessage, PlatformUser, MessageRef, and ClickHandler are declared here for handler typing only — they're implemented at runtime by @copilotkit/bot and its adapters. @copilotkit/bot-ui has no runtime dependency on them.

bind() — the Tier-2 escape hatch

Inline onClick handlers are bound by content (component identity + path + serializable props), so a handler can be re-derived after a restart by re-rendering the component. When a handler closes over data that can't be reconstructed from props, wrap it with bind() so the engine persists that small payload explicitly alongside the minted action id:

import { bind } from "@copilotkit/bot-ui";

<Button onClick={bind(handleChoice, { choiceId: "abc123" })}>Choose</Button>;

bind(handler, args) returns a tagged handler; the action registry stores args so a cold-path dispatch passes them back via ctx.action.value. Keep args small — it's the only handler-specific state that survives a restart.

Exports

Runtime: renderToIR, Fragment, bind, and the vocabulary (Message, Header, Section, Markdown, Field, Fields, Context, Actions, Button, Select, Input, Image, Divider). Types: BotNode, BotChildren, ComponentFn, Renderable, Thread, InteractionContext, PlatformUser, IncomingMessage, MessageRef, ClickHandler, and the per-component prop types (MessageProps, ButtonProps, SelectProps, TableProps, TableColumn, …).