You are halfway through debugging on a remote host. A command is still running, but you need another shell to inspect a log. Do you reconnect, pass through the jump host again, and find your working directory all over again?
This small interruption is why I added Duplicate Tab to xtty. It opens an independent SSH connection to the same host in the same remote directory, while the original session stays where it is. Watch that moment in our walkthrough:
I would love to compare workflows: do you use tmux, another terminal tab, an IDE, or something else for a second remote shell? What part still feels unnecessarily repetitive?
I m the developer of xtty, a native macOS terminal for everyday SSH and coding-agent work. It opens saved hosts together, and Duplicate Tab starts an independent SSH connection in the same remote directory. It also supports split panes, selected-pane broadcast input, and sz/rz file transfers.
The Free edition is available for Apple Silicon and Intel at https://xtty.sh/. If you regularly use SSH from a Mac, I d value feedback on one real task: what setup step still interrupts your work, and where would xtty help or fall short? Critical feedback is welcome. No purchase is needed.
Spend your time on the work, not the terminal. xtty is a native macOS terminal for everyday SSH and coding-agent work. Batch-connect to saved hosts, use configured password autofill, transfer files with sz/rz, and work with tabs and split panes. Duplicate Tab opens an independent SSH connection in the same remote directory. Includes broadcast input and coding-agent status. Apple Silicon and Intel. Free edition; optional one-time Pro purchase.