BentoTUI docs

Bentos

registry/bentos/* ships runnable template apps for fast remix.

Responsibility

  • Orchestrate app flow and model-owned state.
  • Compose rooms and bricks into complete experiences.
  • Provide production-oriented starting points instead of toy demos.

Shipped bentos

  • home-screen - starter entry screen with theme picker/dialog examples
  • dashboard - 2x2 metrics/table composition with anchored footer
  • app-shell - canonical workspace shell with command palette and theme flow
  • detail-view - list/detail split and session card
  • dashboard-brick-lab - component showcase and layout test bed

Primary docs emphasis: home-screen, app-shell, and detail-view.

v0.6.0 template and behavior notes

  • bento init is template-first and requires bento init <bento>.
  • The interactive bento flow uses a template picker for named bentos.
  • dashboard-brick-lab propagates theme.ThemeChangedMsg through composed bricks.

Contract

  • Bentos consume rooms and bricks; they do not duplicate those responsibilities.
  • Bentos avoid raw bubbles/* imports (spinner exception, guardrail-enforced).
  • Bento View() should not call theme.CurrentTheme() directly; theme state belongs to the model.