Copy-and-own TUI architecture for Bubble Tea v2.

BentoTUI now ships with a frozen contract: bentos, rooms, and bricks. Apps move faster because responsibilities are explicit and visual semantics are centralized in the Untouchable Theme Engine.

go install github.com/cloudboy-jh/bentotui/cmd/bento@latest

Copy and compose

The CLI copies source into your repository so your team owns delivery. Start with a bento, compose rooms, and paint with bricks while keeping framework validation reproducible. 

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

# Add a validation app and architecture primitives
bento add app-shell panel bar surface list

# Inspect all available bentos, rooms, and bricks
bento list

# Start from copy-and-own source
bento init myapp

Bentos, rooms, bricks

The architecture model is intentionally strict: bentos orchestrate behavior, rooms allocate geometry, and bricks paint reusable UI components.

Bentos

Full app orchestration

Bentos define complete user flows, scenario coverage, and screen-level behavior.

  • Own app-level states
  • Coordinate focus flows
  • Drive validation scenarios

Rooms

Geometry and allocation

Rooms compose layout geometry, split policy, and viewport adaptation across screens.

  • Allocate width and height
  • Use `WithGutter` and `WithDivider`
  • Keep layout deterministic

Bricks

Reusable UI rendering

Bricks render components with stable contracts so teams can upgrade behavior safely.

  • Paint visual components
  • Preserve compatibility
  • Harden ANSI-heavy rendering

Untouchable Theme Engine

Theme semantics are global and non-negotiable at the contract layer. The theme engine removes per-screen color glue, keeps rendering coherent, and makes scenario snapshots meaningful across viewports.

Global semantics

Tokens and style mappings are shared across bentos, rooms, and bricks.

Deterministic validation

app-shell validates scenarios with scenario + viewport + theme + focus + snapshot.

No local drift

Theme behavior is centralized so product teams avoid one-off palette logic.

Defined docs path

The docs set now mirrors the frozen architecture and execution flow. Use these in order when onboarding contributors.

Architecture

Canonical freeze contract, validation tuple, and model boundaries.

Roadmap

Execution priorities, quality gates, and what ships next.

Next Steps

Immediate tasks for validation breadth and contract hardening.