brand-ui — MessageFeedback

import { MessageFeedback } from "@elabs-ai/components-ai";

Install

npm install @elabs-ai/components-tokens @elabs-ai/components-ui @elabs-ai/components-ai

Skipping the @source line is the most common first failure: Tailwind does not scan node_modules, so every component renders unstyled. The one-time wiring

Prompt for your coding agent

Paste it into Claude Code, Cursor, Codex or any other coding agent. Text in [brackets] is yours to fill in.

Add the brand-ui MessageFeedback 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 MessageFeedback up before writing code: `npx -y @elabs-ai/components-cli docs MessageFeedback` 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

Expecting it to persist the vote — it emits `onSubmit({ type })`; storage is the host's.
Re-enabling the buttons after a vote — feedback is submit-once, and the root reports it via `data-submitted`.
Putting it on a user turn — feedback is about the assistant's answer.

Works with

Used inside

Message
MessageActions

Pairs with

MessageAction

Examples

6 live examples

Submitted Positive

Submitted (positive) — the chosen thumb stays prominent, controls inert.

Submitted Negative

Submitted (negative).

Compact

Compact — tighter spacing/size for a message action toolbar.

Disabled

Disabled — e.g. while the message is still streaming.

Dark Theme

Dark theme.

API

`MessageFeedback`

compact: truefalse (default)

Prop	Type	Description
`value`	`FeedbackType \| null`	Controlled selected feedback. When set, `onSubmit` is the only updater.
`defaultValue`	`FeedbackType \| null`	Uncontrolled initial selection. @default null
`onSubmit`	`(feedback: { type: FeedbackType }) => void`	Called once with the chosen feedback. No persistence — host-owned.
`disabled`	`boolean`	Force-disable both controls (e.g. while the message is still streaming).
`positiveLabel`	`string`	aria-label for the positive control. @default "Good response"
`negativeLabel`	`string`	aria-label for the negative control. @default "Bad response"

Also accepts: Omit<HTMLAttributes<HTMLDivElement>, "onSubmit" | "defaultValue">, VariantProps<typeof messageFeedbackVariants>