Everyone figured AI would supercharge IDEs — you know, those glossy Visual Studio Code extensions churning out code suggestions like candy from a machine. Slick GUIs, mouse-driven everything, the works.
But here’s the twist. Terminals are exploding. Claude Code cranks out 4% of public GitHub commits — that’s 135,000 a day, doubling every month. OpenCode snags 95,000 stars in two weeks. Developers (69% of ‘em) live in terminals nonstop. This isn’t nostalgia. It’s a platform shift.
Ghostty even flips nonprofit to dodge buyouts. Tectonic.
Why Did AI Pick the Terminal as Its Runtime?
Look. AI agents like Claude Code, Codex CLI, Gemini CLI — they’re all shell-dwellers. Not by accident.
The terminal became an AI runtime nobody intentionally designed, and it turns out to be a really good one.
That’s the killer line from the underground chatter. IDEs suggest. Terminals execute: write, test, log, fix, commit. One environment. No context-switching hell. And with Rust/Go tools like ripgrep (bye, grep), bat (forget cat), zoxide (cd’s smarter cousin), the shell got beautiful without trying. ChromaCat? Turns logs into aurora-shimmering art. Who saw that coming?
Emulators leveled up too — Ghostty at 500fps GPU glory, Kitty’s images, WezTerm’s multiplexer. True color. Ligatures. WebGPU dreams in Rio. Developers sink hours here now. Capable canvas.
But design? Crickets.
Web has Material. HIGs everywhere. Accessibility baked in.
Terminals? Vibes. A 1983 ACM paper. Base16 colors. clig.dev skips TUIs as ‘niche.’ Awesome-tuIs lists apps, not principles.
Massive gap. Opportunity screaming.
I’ve built five production TUIs across frameworks. Learned the hard way: cells rule. Waste one column? That’s 1% of screen gone. Pixels forgive; grids don’t.
The Seven Layout Architectures That Win
Successful TUIs cluster into seven patterns. Studied 23 exemplars. Patterns emerge.
First: Persistent Multi-Panel. Lazygit, btop, Unifly. Fixed spots — network top-right forever. Eyes train. No surprises unless user says so. Spatial memory magic.
Second: Stacked Lists. Scrollable stacks with modals. Bottom-heavy: main list dominates, previews peek above. Think bottom-up reading flow (terminals scroll that way). yazi nails file browsing here.
Third: Wizard Flows. Linear steps, full-width. Progress bar top. Back/forward keys. Great for setup hell — onboarding without overwhelming.
Fourth: Canvas + Overlays. Infinite-ish canvas (zoom/pan), popups float. Rare, but hex editors crush it. use terminal’s grid for precise placement.
Fifth: Tabbed Workspaces. Tabs top/bottom, switch with alt+arrows. Multiplexers like tmux evolved this. Scales to power users.
Sixth: Split-Resizable. Drag (vim-style) to resize panes. Dynamic, but anchors prevent chaos.
Seventh: Full-Screen Modal Trees. Nested expanders. Like htop’s tree view. Hierarchy without panels eating space.
Pick wrong? Users bail. Mental model shatters.
And navigation — keyboard reigns. Vim hjkl, or arrows. But consistent: / to search everywhere. ? for help. Esc clears. Borrow that.
Colors? Base16 solid start — 16 semantic roles (base, foreground, etc.). But extend: info (cyan), warn (yellow), error (red), success (green). Gradients? Kitty supports. Use sparingly — density first.
Components: Tables with zebra stripes (alt rows shaded). Progress bars as block chars (█ ▓ ▒ ░). Spinners from Unicode. Borders with box-drawing chars — thick for sections, thin for cells.
Accessibility? Terminals degrade gracefully — slow links? Text-only shines. Screen readers parse grids via status lines. But no standards. Mandate readable contrasts (WCAG-inspired: 4.5:1). VoiceOver mappings.
Is TUI Design Just Web Design in Monospace?
Nope. Fatal mistake.
Web scrolls infinite, nests divs. Terminals? Fixed grid. Reflow on resize hell — design for 80x24 baseline, scale up.
Keyboard-first: no hover. Focus visible always (inverse bg).
Information density: cram smart. Abbreviations consistent (e.g., ‘del’ not ‘delete’). Tooltips via long-press or key.
My unique angle — this mirrors 1990s X11 era. Before web ate desktops, apps built native widget kits (Motif, GTK). Terminals need that: a cross-framework TUI Kit. Predict: Ratatui + Charm ecosystem births it by 2025. OpenCode’s stars signal demand.
Corporate spin? Nah, this is dev-driven. No VC fluff. Pure utility glow-up.
Built my system: shared primitives (Button, Table, Modal) across apps. Reuse slashed bugs 40%. Mental load? Zero.
Start here. Fork awesome-tuis. Add HIG. Ship.
Terminals aren’t dying. They’re the AI frontier’s control room.
🧬 Related Insights
- Read more: Forget Direct AI Prompts: Interview It First and Watch Magic Happen
- Read more: Cursor’s Self-Hosted Agents Finally Crack Open Fortune 500 Firewalls
Frequently Asked Questions
What are TUIs and why now?
Text User Interfaces — full-screen terminal apps. Surging because AI agents live in shells, modern tools prettify output, emulators render like GPUs.
How do I start designing TUIs?
Master seven layouts: multi-panel, stacked lists, etc. Obsess over cells. Use Base16 colors, Unicode components. Build in Ratatui or Bubble Tea.
Will TUIs replace IDEs?
Not fully — but hybrid. Agents handle grunt, TUIs orchestrate. Expect terminal-first dev by 2026.
