Coding Agents Make Native GUIs Cheap Enough to Replace Terminal
Developer advocate Thomas Ptacek is calling on programmers to stop building text-based terminal interfaces and use coding agents to ship native GUI apps instead, an argument Simon Willison endorsed on 21st August 2026.

👁 116 reads
Developer Thomas Ptacek published a call on 21st August 2026 for programmers to abandon text-based terminal user interfaces (TUIs) and build real native apps instead, arguing that coding agents have reduced the cost of producing a usable GUI to near zero.
- Thomas Ptacek argues that coding agents have cut the cost of building a native GUI to near zero, making terminal UIs an unnecessary compromise
- Simon Willison says he has been using two vibe-coded macOS menu-bar apps - a bandwidth monitor and a GPU monitor - daily since building them in March
- Ptacek's direct challenge: turn one of your existing command-line tools into a native app, because the experience will change how you think about UI development
Simon Willison amplified the argument on his weblog, noting that he had been running two vibe-coded macOS task-bar apps daily since March - one for bandwidth monitoring and one for GPU monitoring - with both holding up in everyday use. Willison acknowledged he has not yet made a habit of reaching for native UIs on all his projects, but wrote that he is “running out of excuses.”
The core of Ptacek’s case is economic: the traditional reason developers default to a command-line interface is that building even a modest GUI takes time and effort that rarely feels justified for a small personal tool. Coding agents change that calculation by handling much of the boilerplate, leaving the developer to describe what they want rather than write every widget by hand.
“If you haven’t tried your hand at turning one of your 500 throwaway CLIs into a native app, you’re doing yourself a disservice. Go build a native UI. It’ll probably change the way you think.”
The practical implication for anyone who builds or uses AI-assisted tools daily is straightforward: the threshold for choosing a native interface over a terminal script has dropped significantly. A monitoring script, a file-processing helper or a local API wrapper that previously lived in a terminal window can now be wrapped in a proper GUI in roughly the same session - meaning the old default of “CLI because it’s faster to build” deserves a second look before the next small tool gets started.
Google · Your sourcesQuantslant higher in your Google - one clickAdd to preferred sources →More on this from QUANTSLANT
ai tools·Linus Torvalds credits AI with grunt-work on kernel debug session

