BentoTUI

Build full Go TUIs fast.

BentoTUI is the fastest way to build full Go TUIs using copy-and-own bricks and recipes, import-only room layouts, and runnable bento templates.

Current docs snapshot: v0.6.0

Ship in days, not weeks

BentoTUI gives Go teams a production-oriented TUI system: copy-and-own bricks and recipes, stable room contracts, and runnable bentos to remix quickly.

# Install BentoTUI and CLI
go get github.com/cloudboy-jh/bentotui
go install github.com/cloudboy-jh/bentotui/cmd/bento@latest

# Initialize a named bento template
bento init app-shell

# Start from a runnable template app
go run ./registry/bentos/home-screen

# Copy a brick into your app
bento add card

Bricks, recipes, rooms, bentos

Use Bento vocabulary end-to-end: copy bricks and recipes into app code, compose with room contracts, and launch full bento templates for rapid delivery.

Bentos

Full app orchestration

Runnable template apps under registry/bentos/* let teams remix full experiences quickly.

Start with home-screen
Remix app-shell
Ship serious shells fast

Rooms

Geometry and allocation

Import-only layout contracts from registry/rooms keep geometry stable and predictable.

Geometry only
No theme ownership
Deterministic composition

Bricks

Reusable UI rendering

Official UI blocks are copied into your codebase with bento add <brick>.

Copy and own source
Adapt without lock-in
Upgrade on your timeline

Reliable by design

Guardrails enforce clean boundaries so teams avoid architecture drift: rooms stay geometry-only, bricks do not import bricks, and app-level theme state is model-owned.

Copy-and-own UI

Bricks and recipes are copied into your repo so your team owns behavior and release timing.

Import-only layouts

Rooms stay stable as geometry contracts with no color or theme decisions.

Template-first CLI

v0.6.0 standardizes `bento init <bento>` and keeps bento templates first-class.

Defined docs path

Follow the updated docs IA for current APIs, install catalogs, and rendering contracts.