OpenTUI

Use this when the deliverable is a CLI that needs real UI - panes, scrolling, live diffs, key handling - rather than another round of chalk plus readline; the React binding means you can reuse component habits and state patterns you already have. Install `@opentui/core` for imperative control and add `@opentui/react` or `@opentui/solid` only if you want a reconciler, and pair `@opentui/keymap` with it before you hand-roll key dispatch. Two traps: it is FFI to a Zig binary, so Bun is the happy path and Node needs 26.4.0 with --experimental-ffi and --allow-ffi; and before you write any code run `npx skills add anomalyco/opentui --skill opentui`, because the maintained agent skill will keep you off deprecated element names.

Why it is here. It is the first terminal-UI stack that treats React and Solid as first-class renderers over a native core instead of a JS reimplementation, and OpenCode shipping it to millions of users is about as strong a production proof as a TUI library gets. The fact that it publishes its own agent skill puts it ahead of nearly every component library in this index on agent-readiness.