brand-ui — PermissionModeSelect

import { PermissionModeSelect } 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 PermissionModeSelect 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 PermissionModeSelect up before writing code: `npx -y @elabs-ai/components-cli docs PermissionModeSelect` 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

Shipping a CLI's mode vocabulary as a type union — the modes are app-defined data, not a library enum.
Rendering a mode without its consequence sentence — an unstated effect is the failure this component exists to prevent.
Marking the in-force mode by colour alone — the current marker must reach the accessible name.
Using it for a single tool call — that is ApprovalCard; this is the policy that decides how often ApprovalCard appears.

PermissionModeSelect — the standing-permission-policy chooser. Distinct from ApprovalCard/Confirmation: that renders ONE per-call decision; this renders the standing POLICY that decides how many of those decisions ever get asked. The mode vocabulary below is example data only — the component hardcodes no agent's mode names.

Works with

Used inside

Pairs with

Examples

2 live examples

Selecting A Different Mode

Selecting a different mode reports the new id without moving the "Current" marker.

API

`PermissionModeSelect`

Prop	Type	Description
`modes`required	`PermissionMode[]`
`value`	`string`
`defaultValue`	`string`
`onValueChange`	`(id: string) => void`
`currentId`	`string`	The mode currently in force, marked distinctly from the highlighted one.

Also accepts: ComponentProps<"div">

Theming

The tokens each state resolves to. Change the token and every theme follows.

State	Token
selected	`border-primary on the chosen mode's card`
surface	`bg-card per mode row, border-border at rest`
consequence	`text-meta text-muted-foreground — the sentence saying what the mode permits`