Branching thread
ProA conversation that keeps every version: editing a message or trying again starts a branch beside the original, ‹ 2 / 3 › moves between versions, and everything after follows the branch you choose.
pnpm dlx shadcn@latest add @caliper/branching-threadConversation
1 fork on this path- Write a one-line subject for an email telling customers about our price change.
Halden Assistant
A heads-up about your Halden plan from 1 December.- Make it calmer and say that most people pay the same.
Halden Assistant
From 1 December, most plans stay the same price. Here’s the detail.
When to use #
Use it for
- Chat assistants where people refine questions.
- Comparing answers without losing any.
Skip it when
- Support chat with a human; edits there should not fork.
Installation #
pnpm dlx shadcn@latest add @caliper/branching-thread
Adds its 8 files to components/ui/, each with its own stylesheet, and installs their packages. Pro installs with your access token, set up once per project. See Pro access. The first part also adds Caliper UI’s tokens; import them once as in Installation.
Usage #
Import it from your copy of the source. The example behind the preview comes with the source. It is built from activePath and BranchingThread.
import { activePath, BranchingThread } from "@/components/ui/branching-thread"
The worked example comes with Pro
The 34-line example behind the preview opens here with a Pro or Team licence.
API reference #
activePath
component
No props of its own; it accepts the native props of its root element.
BranchingThread
component
Accessibility #
It exposes group and status semantics, with aria-labelledby, aria-hidden and aria-label kept in step with state. Changes that matter are announced through a live region.
Motion #
It declares no animation in its component source. Any transition comes from its stylesheet, which uses the duration tokens that collapse to instant under prefers-reduced-motion.