You’ve probably got five terminal windows open right now. One is running a build, another is watching server logs, and three are connected to different Raspberry Pis and ESP32s. You’re manually typing screen /dev/tty.usb... and praying you remembered the right baud rate.
We’ve all been brainwashed into thinking that because a tool runs in the terminal, it must be the optimal way to do things. But when you’re managing a bench full of Single Board Computers (SBCs), the cracks start to show. We treat repetitive manual configuration as a badge of honor, when it’s actually just a tax on our attention.
CLI tools like tio and screen are undeniably powerful. They are scriptable, lightweight, and deeply customizable. But power without context is just friction. The explosion of cheap, diverse hardware has made baud rate diversity a hidden bottleneck. You aren’t just writing commands; you’re acting as a human switchboard operator for your own devices.
The CLI purists will tell you that a GUI is just a crutch. But when you’re juggling five devices with varying specs, a crutch is exactly what your broken workflow needs.
Enter a new modern serial console for macOS, written in Swift and based on libghostty. It doesn’t try to reinvent serial communication; it just makes the interface incredibly easy to steer. A simple dropdown menu for baud rates. Support for custom, higher frequencies. A modern interface that gets out of your way and lets you actually debug.
True productivity isn’t about doing more things; it’s about eliminating the friction of doing the things you already do.
If you debug multiple embedded systems daily, this isn’t just a nice-to-have aesthetic upgrade. It saves you minutes per session—time that compounds into hours over a project. More importantly, it eliminates the silent killer of embedded development: errors from misconfigured serial connections. No more guessing if you set it to 115200 or 9600.
Stop fighting your tools. The hardware landscape has evolved, and it’s time our debugging interfaces caught up. Sometimes, the most innovative thing you can do is just build an interface that actually works.
FAQ
Q: What about scripting and automation? CLI tools can be piped and automated.
A: You're right, CLI wins for CI/CD pipelines. But for interactive, multi-device debugging sessions where you need to quickly glance at logs and tweak settings on the fly, a GUI drops the cognitive load to zero.
Q: How does this actually save time?
A: It removes the lookup step. No more checking device paths, typing out long commands, or guessing baud rates. You click, connect, and debug.
Q: Is this just a pretty interface for lazy developers?
A: If wanting to connect to five different devices without memorizing syntax makes me lazy, then yes. Efficiency isn't laziness; it's protecting your mental bandwidth for the actual engineering problems.