Waste your life wrestling with terminals—or build something that matters?
Wasted configuration time.
Cluttered interfaces.
AI agents forced into every corner.
Remote servers requiring extra software.
Tools that promise control—but demand more attention.
That is what too many modern terminals have become.
Your terminal should not try to become Iron Man.
It should work like JARVIS.
The terminal is not the hero.
It should be quiet, prepared, and out of the way.
XTTY is built around that idea.
Open the servers you need together.
Reach production through a jump host.
Let macOS Keychain handle recurring password prompts.
Duplicate a remote tab and restore its directory.
Keep remote sessions together.
Broadcast only to selected panes.
See coding-agent status at a glance.
Keep using what already works:
OpenSSH.
~/.ssh/config.
Saved machines.
Local shells.
Tabs.
Split panes.
XTTY.
Stop working for your terminal.
Build something that matters.
xtty.sh
Replies
@jian_xu9 Hi Jason, what I find most annoying is having to repeat the same setup every time I start working. Automating those small steps would make the whole experience much smoother.
@zulma_cink That’s exactly the kind of friction I want xtty to remove. When you say “the same setup,” which steps are you repeating most often—opening the same local project, reconnecting to an SSH host, returning to the working directory, starting a coding agent, or something else? I’d like to understand the sequence before deciding what should be automated.