Reading take
HRA v0 is not a Codex TUI.
A new terminal dashboard is rarely the product now that agents can summon native UI. HRA v0's published job is a Codex metaharness: authorized accounts, a durable task graph, and recovery after a restart.
Sources fetched August 26, 2026.
Stop Making TUIs
Ptacek keeps the CLI and drops the TUI default
On August 20, 2026, Thomas Ptacek published Stop Making TUIs. He writes, “We build terminal interfaces because we have to, not because we should.” Command-line interfaces stay useful for scripting and remote work. Terminal user interfaces inherit 1970s constraints: they fight the terminal for scrolling, selection, drag and drop, floating windows, and images that native widgets already provide.
Agents changed the cost. He summoned personal SwiftUI apps from skills and templates, then concluded you can reasonably default to native interfaces and they will be kind of good. “Building a CLI is almost always a good idea. Building a TUI almost never is.” SSH still wants a CLI that a local GUI can drive. It does not require shipping another TUI.
The essay is about personal software defaults. It does not mention HRA.
HRA v0
HRA v0 publishes a coordination loop
The live archive states the product job in the words it already uses: pair authorized Codex accounts, keep parent and child work in one durable graph, and recover the work after a restart instead of only restoring a window.
The Hraness page What is an agent harness? says an agent harness gives a model a place to work. On that page, Hra is the loop: a Codex metaharness that coordinates parallel sessions, review, and recovery after a window dies. The model still chooses the next tool call. Hra keeps the work from vanishing when the chat does.
Credentials and provider sessions remain isolated on the Mac. The hosted surface receives bounded coordination and review state. That is custody and recovery, not terminal chrome around Codex.
TUI habit vs published job
A metaharness is not ASCII chrome
ASCII chrome is a TUI around Codex: panes, progress bars, and in-band borders. HRA v0's published job is the loop that keeps several Codex harnesses attached to one review path after a chat or window ends.
Ptacek's claim is that native UI got cheap. That claim does not assign HRA a TUI, and it does not forbid HRA a desktop or web surface. Direct is a different surface on another host: it names repeatable app states so a browser agent can reach them, and it does not click the page.
This page does not claim that HRA cannot have a UI, or that Ptacek wrote about HRA. It only contrasts TUI habit with the job the fetched HRA pages actually state.
Fetched pages