A collection of beautifully designed, accessible, and customizable terminal UI components. Built on Ink and OpenTUI. Works with shadcn/ui.

How do I publish components with termcn?

Add or edit components under registry/bases/ink/ or registry/bases/opentui/, register them in registry.json, run pnpm registry:build (which refreshes public/r/), then deploy. Consumers install with npx shadcn@latest add against your published registry URL.

Is termcn open source?

Yes. The source is on GitHub and released under the MIT License.

Select

Single-select dropdown with arrow-key navigation

Ink OpenTUI

Terminal

Installation


$ pnpm dlx shadcn@latest add @termcn/ink/select

Usage

import { Select } from "@/components/ui/select";

<Select
  label="Choose a framework"
  options={[
    { value: "next", label: "Next.js" },
    { value: "remix", label: "Remix" },
    { value: "astro", label: "Astro" },
  ]}
  onChange={(value) => {}}
/>

API Reference

Select

Prop	Type	Default
`options`	`SelectOption<T>[]`	`required`
`value`	`T`	-
`onChange`	`(value: T) => void`	-
`onSubmit`	`(value: T) => void`	-
`label`	`string`	-
`cursor`	`string`	`"›"`
`cursorColor`	`string`	-

Notes

Accessibility

termcn exposes the following behavior through Ink's terminal accessibility APIs. This is not a browser ARIA or general WCAG-conformance claim.

Keyboard: Arrow keys move inside the composite; Home / End select the first or last enabled item; Enter / Space activate, select, or toggle; Escape cancels or closes an owned surface; Tab / Shift+Tab move between termcn/Ink focus targets.
Focus and composition: Input is active only while the component's focus target is focused, enabled, active, and inside the topmost focus scope.
Screen reader: Ink labels and semantic state expose the component without relying on visual styling alone.

Radio Group Tag Input

On This Page

Installation Usage API Reference Select Notes Accessibility

Edit this page Follow @shadcnlabs Join community