MyShell
Use case
MyShell for remote SSH
MyShell is built for remote SSH work. Connect with your system OpenSSH when available — ~/.ssh/config, keys, and known_hosts — keep sessions in a grid, and use help that follows the OS on each connection.
What you get
- Local + SSH sessions with quick starts and groups
- Prefers system OpenSSH; built-in stack as fallback on Windows and Linux
- Offline help adapts to the remote OS (Ubuntu, CentOS, macOS, Windows, …)
- Keep-alive profiles for wrangler, pnpm, and other long-running remotes
- AI and tasks include one-click Run into the active SSH session
Who it’s for
Developers and DevOps who live in cloud VMs, bastions, and staging hosts — and want help, tasks, and AI on the same machine as the shell, not only in the editor.
FAQ
Does MyShell use my existing SSH config?
When system OpenSSH is available, MyShell prefers it so ~/.ssh/config, keys, and known_hosts work as you expect.
Can I mix local and remote sessions?
Yes. Run local shells and SSH remotes in the same workspace, including a multi-column grid.
Is Cloud required for SSH?
No. SSH and local shells work with Desktop offline. Cloud is optional for sync and hosted AI.
Try MyShell
Native desktop for macOS, Windows, and Linux. $39 one-time Desktop with BYOK AI. Optional Cloud for sync and hosted AI. 14-day trial.