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.

Tool Call

Displays an AI tool invocation with status indicator, args, result, and elapsed time

Ink OpenTUI

Terminal

Installation


$ pnpm dlx shadcn@latest add @termcn/ink/tool-call

Usage

import { ToolCall } from "@/components/ui/tool-call";

<ToolCall
  name="search_codebase"
  args={{ query: "handleSubmit", maxResults: 10 }}
  status="success"
  result="Found 3 matches in src/components/"
  duration={245}
/>

API Reference

ToolCall

Prop	Type	Default
`name`	`string`	`required`
`args`	`Record<string, unknown>`	-
`status`	`"pending" \| "running" \| "success" \| "error"`	`required`
`result`	`unknown`	-
`duration`	`number`	-
`collapsible`	`boolean`	`true`
`defaultCollapsed`	`boolean`	`true`

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: Enter / Space activate the focused action when enabled; Escape dismisses or cancels when supported; Tab / Shift+Tab move through 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.

Tool Approval OpenTUI

On This Page

Installation Usage API Reference ToolCall Notes Accessibility

Edit this page Follow @shadcnlabs Join community