import { GroupedParts } from "@elabs-ai/components-ai";npm install @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-aiPaste it into Claude Code, Cursor, Codex or any other coding agent. Text in [brackets] is yours to fill in.
Add the brand-ui GroupedParts component (from @elabs-ai/components-ai) to this project. 1. Read https://elabs-ai.com/llms.txt first: it maps every package and the rules. If you can use MCP servers, connect https://elabs-ai.com/mcp and use its search, docs and tokens tools. If not, run the same lookups in the terminal: `npx -y @elabs-ai/components-cli search "<what you need>"` and `npx -y @elabs-ai/components-cli docs <Component>`. 2. Look GroupedParts up before writing code: `npx -y @elabs-ai/components-cli docs GroupedParts` prints its real props, variants, what it pairs with and what to avoid. 3. If @elabs-ai/components-ai is not installed yet: `pnpm add @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-ai` (or `npm install @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-ai`). If this is the first brand-ui package in the project, wire it once: import `@elabs-ai/components-tokens/styles.css` plus the `themes/light.css` and `themes/dark.css` stylesheets in the CSS entry, add one Tailwind `@source` line per installed @elabs-ai package (Tailwind does not scan node_modules, so without it everything renders unstyled), and wrap the app root in `ThemeProvider` from `@elabs-ai/components-tokens`. 4. Use it here: [the screen or file, and what it should show] 5. Rules: use only @elabs-ai/components-* components and the semantic tokens — no raw colours, no raw font sizes, no arbitrary Tailwind values. Look up each component's real props with the docs tool before you use it; never guess a prop. 6. Done means: the typecheck passes, `npx -y @elabs-ai/components-cli audit src --strict` reports nothing, and you have opened the app and looked at every screen you touched in the light and the dark theme.
Avoid
- Asking the model to emit groups — grouping is a client-side view transform, never an output format.
- Reordering parts to make the grouping tidier — the part order is the record of what happened.
- Rebuilding the reasoning/tool rendering in the render-prop — omit it and the defaults compose Reasoning and Tool for you.
Works with
Used inside
Pairs with
Examples
Streaming
Streaming — a tool is still running, so the trace rolls up to "running" and opens automatically.
Standalone Interaction
Interaction cards never fold — an approval-style part is forced standalone, splitting the trace around it.
Custom Grouping
Custom grouping — group everything into a single trace via a custom groupBy.
Empty
Empty — an empty part list renders nothing (no broken UI).
Dark Theme
Dark theme — trace disclosure + tool cards in dark.
Focus Indicator
Focus indicator on group triggers (#313): Tab to a collapsible trigger and assert the compound indicator's OUTLINE layer (`outlineStyle: "solid"`, `--ring-contour`) that `focus-ring-inset` adds. `boxShadow !== "none"` alone also passes on the legacy `focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-inset` pattern (Tailwind's `ring-2` still paints a box-shadow), so it does not lock the fix.
API
GroupedParts
| Prop | Type | Description |
|---|---|---|
partsrequired | readonly T[] | The ordered message parts to render. |
groupBy | GroupBy<T> | How to group parts. @default `groupPartByType()` |
getStatus | GetPartStatus<T> | Extract a part's status (drives group rollup + streaming affordances). |
children | GroupedPartRenderer<T> | Render-prop switching on `part.type`. Omit to use the default renderers. |