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.

Tag Input

Add and remove tags inline

Ink OpenTUI

Terminal

Installation


$ pnpm dlx shadcn@latest add @termcn/ink/tag-input

Usage

import { TagInput } from "@/components/ui/tag-input";

<TagInput placeholder="Add a tag…" onChange={(tags) => {}} />

API Reference

TagInput

Prop	Type	Default
`value`	`string[]`	-
`onChange`	`(tags: string[]) => void`	-
`placeholder`	`string`	`"Type and press Enter…"`
`maxTags`	`number`	-
`delimiter`	`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: Left / Right move by grapheme, Home / End move to the boundaries, and Backspace / Delete remove one complete grapheme. Enter submits or confirms (Ctrl+Enter in TextArea); Tab / Shift+Tab leave through Ink focus traversal.
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.

Select Tree Select

On This Page

Installation Usage API Reference TagInput Notes Accessibility

Edit this page Follow @shadcnlabs Join community