Mitchell Hashimoto

Things Mitchell Says on Podcasts

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 as CEO and CTO before leaving in 2023. Started Ghostty and libghostty, a terminal emulator and an embeddable terminal library, and co-founded Superlogical. Writes at mitchellh.com. Appears as a guest on Fragmented, PodRocket, Scaling DevTools, The Changelog, Software Unscripted, Fallthrough and The Pragmatic Engineer, discussing Ghostty and his agentic coding workflow.

Where to Find Them

Mitchell Hashimoto writes Fragmented - AI Developer Podcast . They have also been a guest on The Changelog (4 times) , Software Unscripted (2 times) , The Stack Overflow Podcast (2 times) , Fallthrough (2 times) , devtools.fm: Developer Tools, Open Source, Software Development , The Standup with ThePrimeagen , Platform Engineering Podcast , Latent Space , Scaling DevTools , The Pragmatic Engineer , Software Engineering Radio - the podcast for professional software developers , PodRocket , The InfoQ Podcast and Software Misadventures .

Recently: “Mitchell Hashimoto Reinvents the Terminal... Again” on The Standup with ThePrimeagen (November 2026); “PRs NOT Welcome: How Top AI Open Source Projects Are Managing Thousands of Contributors” on Latent Space (September 2026); “310 - Mitchell Hashimoto on Ghostty & His Agentic Coding Workflow” on Fragmented - AI Developer Podcast (April 2026); “310 - Mitchell Hashimoto on Ghostty & His Agentic Coding Workflow” on Fragmented - AI Developer Podcast (April 2026); “Mitchell Hashimoto’s new way of writing code” on The Pragmatic Engineer (February 2026); “How Mitchell Hashimoto Builds Ghostty” on Software Unscripted (February 2026).

What They Said

“ATC for me was always this thing that doesn't fail. You decide to kind of assume that that will be mostly available. … I personally never, through my 2000 hours of flying, had any sort of training on what to do if ATC fully fails. It's basically: switch to the last frequency and talk to the last person you were talking to and hope for the best.” — Mitchell Hashimoto, The Standup with ThePrimeagen

The hosts brought up the FAA ground stop and asked Mitchell, a former hobby pilot, about it. He says pilots are never trained for a total air traffic control failure because it was assumed not to happen.

The Standup with ThePrimeagen · 2026-11-20 Permalink → Listen →
The Standup with ThePrimeagen Around 53:26 into the episode
Mitchell Hashimoto

…of the belief is that if it's not broken, don't fix it. You know, and one of the, I think, best examples of that that I had like personally was this. This is what I flew originally, is this plane. And most piston engine planes still start up. Their engine still runs on Magnetos. You know, actually.

TJ DeVries

I just got to get one in.

Mitchell Hashimoto

…for my own aircraft. And I'm like, oh, yep, that one's fucking broken. And then you go replace it. But like these things shouldn't fail that often, right? So like there's antiquated stuff everywhere. The funny thing is you don't learn as a pilot really how like these systems of ATC work. It's actually through all the failure scenarios you're meant to handle. I mean like you're you sort of like ATC for me was always this thing that doesn't fail. You decide to kind of assume that that will be mostly available. There's we did training for like if if the tower at a at a airport fails like if like how do planes land at an airport without any tower controlling them we do stuff like that. I personally never through my 2000 hours of flying had any sort of training on what to do if like ATC fully fails. Like it's basically like switch to the last frequency and talk to the last person you were talking to and…

Speaker 3

Well, okay, so people just had to kind of like, is this, is your experience, I guess, more common in the sense that a lot of people just wouldn't know what to do? Or the people flying commercially, do they have like already like a playbook for if this were to be aware of? I hope

Mitchell Hashimoto

they have a playbook. I would, I, I like actually really want to know, but they do have a lot of redundancy in their communication. So I'm sure like they have, they have a direct connection to like their dispatch. So like a United pilot could be like, could just call their United dispatch and be…

Speaker 3

also have Starlink now. So they could also do radio. There's internet as well. Yeah.

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.
“Claude Code … is driving a really crazy amount of terminal usage. I thought it was actually a red flag, because it made me ask why, multiple times. Why are they using a terminal? Because the simpler programming model actually makes it faster to develop software. There's less sandboxing. Web and even OS processes are so much more locked down by default than your terminal. It usually just has full privileges to a huge surface area of your system.” — Mitchell Hashimoto, The Standup with ThePrimeagen

Asked why he moved from Ghostty to a commercial product, Mitchell said agentic coding tools changed the market for terminals. He read the surge in terminal use as a warning sign rather than simply good news.

The Standup with ThePrimeagen · 2026-11-20 Permalink → Listen →
The Standup with ThePrimeagen Around 31:08 into the episode
Mitchell Hashimoto

…like a cool project and it would like, I want to build this thing great, but like it's because I live in the terminal, it's great. But like the total group of, I mean, the absolute value, but also the relative value to the number of developers of terminal users, I felt was going down. And then the

Speaker 3

TAM was pretty small. I'll give you that. The TAM is not large for terminals.

Mitchell Hashimoto

Yeah. And of course, like, I didn't even, I guess maybe like background, I thought about it that way, but there was never any commercialization strategy here. So like I didn't. Care. And then, you know, along the way, that ended up not sort of being true in a sense. Like, I mean, cloud code probably being the big reason for this. Like, whatever your opinion on agentic anything is, like, it's driving a really crazy amount of terminal usage. And I thought, I thought about this in a couple of ways. Like, one, it was really exciting because I'm building a terminal. Two, I thought it was actually a red flag because it made me ask like why multiple times. Like, why are they using a terminal? And it's like, oh, because a bunch of reasons. Like, it's the simpler programming model actually makes it faster to develop software. There's less sandboxing. Like, web and even OS processes are so much more locked down by default than like your terminal. It usually just has like full privileges to a huge surface area of your system. So it's

Speaker 3

it makes you look cool. You forgot that one. That's like a very major aspect of using the terminal. I

Mitchell Hashimoto

think you look cool. Yeah. And then also like there was also a part of me that I do love the terminal. So there was a part of me that felt like it had stagnated so long capability wise. Like I looked at other platforms. Like I always view the terminal as like a text-based application platform. And…

Speaker 3

If you don't know who EIEIO is, he makes really kind of cool games. One of them was like a thousand people playing SSH Snake. And he does write, why does the game render Snake Street? Or why does the game render strangely for me? Snake.run makes use of Unicode block elements. Since they were added…

Speaker names come from our own diarization. The position is estimated from where the line sits in the episode.
“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

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.

The Standup with ThePrimeagen · 2026-11-20 Permalink → Listen →
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.

Collections They Appear In