SSH with blocks, your Mac's shells on your iPhone and iPad, one Mac controlling another, and iCloud sync to tie them together.
Type >prod and press Return. Every remote command still gets its own block with its exit code and the remote folder, and the input keeps completing, now against the server.
Pick a key from ~/.ssh, or press Detect and Turm asks the server which of your keys it accepts. Import every Host in ~/.ssh/config in one go.
A password stays in the Keychain only when you ask, and is typed only at the prompt for that host's own user@host, once per connection, so a jump host never sees it. Opt in per host and Turm answers sudo's own prompt for a command you typed with sudo, automatically or with one click.
Switch on Allow remote control on the Mac, then scan its QR code from the app, or type the 8-digit code and compare the 6-digit check code on both screens before you approve.
Macs on your network appear over Bonjour, and over Tailscale you enter the Mac's address. Every paired device gets its own key on an encrypted connection, and you can revoke it from the Mac at any time. If a Mac does not appear, a code fails, or hosts do not sync, the support page has the checks that usually fix it.
Open the shells of a Mac running Turm as blocks, or SSH straight to your servers. The shells keep running on the Mac, and the app lists them, shows their history and lets you type into them.
A key bar puts esc, tab, ctrl and the arrows above the keyboard. On an iPad the sidebar and the session sit side by side.
TurmPair two Macs and the Remote Macs window (Shift-Command-R) lists the other Mac's shells with their state. Type in the bar at the bottom, interrupt with a click, and let Fit to This Window size the shell to what you see.
Each direction is its own pairing with its own key. Letting one Mac control another does not let it control you back, and each can be revoked or forgotten without touching the other.
Files, notifications, sync, server setup, host keys and the iPhone keyboard.
From a folder chip the phone lists that folder on the Mac, and previews images and text. Upload sends a file back, which needs Allow file uploads on the Mac: it is off until you turn it on and choose the one folder it may write to.
A command that finishes in a Mac shell you are attached to posts a notification with its exit code and how long it took, while the app is running in the background. iOS delivers nothing once it suspends the app, and Turm does not use a push server to get around that.
Then your SSH hosts, global shortcuts, remembered passwords and stored keys follow you between Mac, iPhone and iPad through iCloud Keychain, which is end-to-end encrypted. Remote Access pairings and project shortcuts stay on the device that made them.
One click copies Turm's zsh, bash or fish hooks into ~/.turm/shell over the connection you already opened, with no second login. The server's .zshrc and .bashrc are never edited, and a newer Turm offers an Update.
The first connection from the iPhone or iPad shows the server's host key to trust. Every connection after is checked against it, and a server that presents a different key is refused.
esc, tab, arrows and symbols sit above the keyboard. ctrl and alt apply to the next key or lock with a double tap, arrows repeat when held, and a drag pad moves the cursor.
Pick a topic, or search everything remote.
Connect with a name, and every remote command keeps its block while the input works against the server.
>prod opens a saved host with its user, port and key, and >prod uptime runs a command there. Hosts from ~/.ssh/config and >[email protected]:2222 work too. > file with a space is still a redirect.
Remote folders and files, the commands on the server's PATH, its environment variables, git branches and tags, and its processes. Unknown commands still turn red.
package.json, Cargo.toml, Makefile, compose files and Turm.json are detected on the server, and their actions run in the remote shell.
A file or image you paste or drop is uploaded to a private folder in the server's temp directory, and its path is inserted.
Click the host chip to save the server, copy its address or ssh command, or disconnect. The folder chip copies the remote path, or a user@host:path for scp.
After a second ssh hop, or with your own ssh function, blocks and exit codes still work but completion, git and the project bar are off. When a connection ends Turm returns to the local shell, and one that dropped while idle leaves a Disconnected block with ssh's last message.