golang-tui

Define a model struct, implement Init, Update, and View methods following the Elm Architecture, then run it with tea.NewProgram. Handle tea.WindowSizeMsg for dimensions and wrap all I/O in tea.Cmd functions so Update never blocks.

Define lipgloss.Style values at package level and apply them with Render, using Width, borders, padding, and JoinHorizontal or JoinVertical for layout. Use lipgloss.Width or ansi.StringWidth instead of len() to measure styled strings correctly.

Freezing usually means blocking I/O or time.Sleep inside Update; move that work into a tea.Cmd. A blank screen typically means WindowSizeMsg was not handled, leaving components with zero dimensions.

Use teatest for integration tests and go-snaps or go-snap with golden files for snapshot testing of rendered output. Pin TERM and color profile in tests so ANSI sequences stay deterministic across runs.

Yes, tea.SetClipboard writes via OSC 52 and tea.PasteMsg delivers bracketed paste content. For wider coverage, combine OSC 52 with a native clipboard library like atotto/clipboard as a fallback.

Avoid it for simple one-shot scripts where plain stdout output suffices, or when targeting environments that strip escape sequences like old multiplexers without passthrough. Heavy raster image rendering may also hurt frame time in latency-sensitive TUIs.