MH Mitchell Hashimoto Mitchell Hashimoto Software developer and co-founder of HashiCorp, where he was part of the engineering team behind Vagrant, Packer, Consul, Terraform, Vault and Nomad and served...

“Our point of view is every UI element, every interaction has to be API driven, so that agents could drive it, but also so that all the programs you write could automate it. Right now, I think it's too bolted on. You can't ship a button without that button actually having an API associated with it. You can't ship a table view update without the data source behind it also being queryable via an API.”

The Standup with ThePrimeagen · Hands-On Engineering Podcasts · November 2026

“Our point of view is every UI element, every interaction has to be API driven, so that agents could drive it, but also so that all the programs you write could automate it. Right now, I think it's too bolted on. You can't ship a button without that button actually having an API associated with it. You can't ship a table view update without the data source behind it also being queryable via an API.” — Mitchell Hashimoto, The Standup with ThePrimeagen

Context

Mitchell was describing how Rex, his new terminal product built on Ghostty, will add non-terminal UI. He says today the only way to make a GUI programmable is to hook into accessibility features, and that agent and script control has to be built in from the start.

Transcript

The Standup with ThePrimeagen Around 37:37 into the episode
Mitchell Hashimoto

yeah, we did it today.

TJ DeVries

Okay, nice. That was today. Yeah. And so you have like UI.pick or UI.input. And it's like, yeah, those are pretty much all I need for 99% of the things that I would do inside of an app is I want to pick things from a list. Yeah. Yeah.

Mitchell Hashimoto

And there's like other philosophical beliefs that I sort of have around the UI, which is sort of that right now, the only way to make a GUI programmable is to sort of hook into accessibility features, either use or abuse, depending on your point of view, the accessibility features of an operating system. Like our point of view is every UI element, every interaction has to be API driven, has to be defined by an API so that the AI focus is so that agents could drive it, but also so that all their programs you write could automate, you could drive it as well. Right now, I think it's too bolted on. And so for us, you can't define it. We haven't shipped the UI stuff yet, but we have experimental versions of it. You can't ship a button without that button actually having an API associated with it. You can't ship a table view update without the data source behind it also being queryable via an API. Forcing that at the metaphorical operating system layer, although this is not in the app space, is what we're trying to do. And the crazy thing I've said is the crazy thing is if people agree with this and it picks up traction, and one of the things I would love to burn money on is hiring a…

Speaker 3

How long do you think you are from that kind of goal of this, of what you just said? How long do you think you are from that state? The

Mitchell Hashimoto

OS side of things.

Speaker 3

Even experimental.

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.

More from The Standup with ThePrimeagen