wayneeseguin

I've published a new, general-purpose terminal specification that gives any program a way to tell the terminal what it's doing: idle, working, waiting, finished, or failed, and why. It is easy to implement on both sides. I've written more about why: mitchellh.com/writing/progra… The problem this solves is generic and applies in compelling ways to all sorts of use cases (e.g. package managers, build tools), but it really rears a hideous head when it comes to AI and the "agentic inbox" problem. I found over 250 different agent orchestrators (with various goals) that all individually implement a heuristic based approach to detecting whether things like Claude Code are working, blocked, done, etc. If you look at @herdrdev's commit history, you can see around 10 compatibility changes to detect Claude Code within just the past 3 months. (This isn't a dig at Herdr! They're doing great work with what they have, and everyone else is doing the same thing). Heuristics are not the way. And over-indexing on agentic use cases isn't the way, because this problem is really interesting for other tools too: Homebrew, Terraform, Cargo, etc. etc. Proprietary protocols and out of band APIs are not the way. They have an O(N) integration problem and require extra work to work over SSH or within local VMs/containers. The program status specification (OSC 7501) solves this in a reliable, deterministic way that is general-purpose and can be easily adopted by the entire industry. Read more: mitchellh.com/writing/progra…

Beautiful libghostty-based iOS/iPad terminal by @almonk. Libghostty has been blowing up in usage it’s kind of silently behind so many apps now I’ll continue to share more. The idea is working! replay.software/echo

If the Rust community had this mentality more generally, I think I would’ve been more inclined to it (I still simply dislike the syntax subjectively, though). Steve says his experience was kindness that brought him there and for me it was unfortunately the opposite. Snobbery looking down on anyone not using it and a completely irrational feeling culture of rewriting everything. As Steve says, this may be perception more than reality. It may be a small (but obnoxiously loud) minority. It really might. But it was enough that at the time it was my reality and I wanted nothing to do with it. When the TSC post went up yesterday I felt I knew EXACTLY how that was going to go and the internet did not disappoint. As Steve said, the reaction played right into the stereotype and just makes the Rust community look bad while probably also genuinely causing the TSC people stress and angst on a day they should celebrate (launch day!!!). Again, may be a minority, but it sucks it played out exactly like I and others imagined it would, stereotypically. To me, Rust has a culture problem. Or maybe just a perception problem. But, as the post says, perception becomes reality at a certain point. Truly, genuinely, I hope people listen to Steve’s takes. The vocal minority needs to be shut down. Yelling at people doesn’t generally make things better.

100%. Ready to go. The release will probably be on the 26th though so I can take time to enjoy the holidays with my family without stressing about inevitable launch day issues. For those interested: thanks for hanging in there, not long now. Happy holidays y'all. ❤️

I'm looking for someone to help me design and build the Ghostty website. If you know a frontend person or team who understands and loves the terminal experience, please email me. Ideally a full stack thinker who can help guide the automated doc process. Paid, of course.