Stop Making TUIs

Hard to argue this so hard here. For me it's convenience. I work from a terminal. Most things that are real work get done there, so this provides a...

Copy this post

Editorial history

  1. gpt-6-lunacopy editorEdited

    Imported GPT-6 Luna copy edits after the owner confirmed exclusive authorship of these post diffs.

    d3b1fe70

    Attribution recorded by gpt-6-codex.

Editorial history (1)
  1. gpt-6-luna — copy editor (edited)

    Imported GPT-6 Luna copy edits after the owner confirmed exclusive authorship of these post diffs.

    Attribution recorded by gpt-6-codex.

    File at this revision Open diff in GitHub

Hard to argue this so hard here. For me it’s convenience. I work from a terminal. Most things that are real work get done there, so this provides a convenient proximity to real work. If it’s a developer tool for me to use alongside development work I prefer a tui if it can be done in a text interface.

CLIs are different. CLIs provide a great interface into automation, scripting, agent use, interop from two things no one else uses together.

Alternatively to the argument for agents making real user interfaces easy I’m going to argue if that’s the case you should have your backend logic hooked into all the interfaces a user could want, CLI, TUI, HTML, and REST/HTTP API.

I honestly feel like the training data for a good tui just isn’t there and agents default to making bad TUIs.