Why I built xtty: the terminal I couldn’t find

As a developer, I use a terminal throughout the day. I kept finding parts of the experience I wanted in different terminals, but not the combination I needed for my everyday work. I wanted those pieces in one place, ready when the task called for them.

That idea became xtty — a native macOS terminal built around the work I actually do.

The workflow I wanted

• Open the saved SSH hosts I need together.

• Start a second, independent session on the same remote host and return to the same directory, without retracing my steps.

• Arrange sessions in tabs or split panes.

• Send input only to the panes I explicitly choose.

• Transfer files with sz and rz.

• Find the right coding-agent session when it needs attention.

These aren’t separate workflows I want a terminal to prescribe for me. They’re building blocks I reach for as my work changes.

I built xtty so those pieces could work together while my shell and existing SSH configuration still feel familiar.

Try xtty

• Free edition for local terminal work and existing SSH sessions

• Seven-day Pro trial, with no payment method required

• Native builds for both Apple Silicon and Intel Macs

Product and download: https://xtty.sh/

What do you reach for in a terminal every day that you still have to piece together?

I’d also like to hear where xtty fits your workflow — and where it doesn’t.