Sherpa support.

Confirm cellular access is enabled for Sherpa and that your VPN, if needed, is connected. Open the machine in Sherpa and use Check reachability. Share its result and the connection history with support.

A TCP timeout occurs before SSH authentication. A successful reachability check confirms a network connection can open, but does not establish that SSH login will succeed. Sherpa reports these stages separately.

The key manager supports OpenSSH Ed25519 keys, including passphrase-protected keys, and unencrypted PKCS#1 RSA PEM keys of at least 2048 bits beginning with -----BEGIN RSA PRIVATE KEY-----. RSA authentication uses RSA-SHA2 signatures.

Encrypted RSA PEM, OpenSSH-format RSA, PKCS#8 RSA, hardware-backed keys, and keyboard-interactive authentication are not currently supported. Never email a private key to support.

Add a key once in Keys, then select it in each machine's authentication settings. The key manager shows its fingerprint and which machines use it. Reassign or remove those machines before deleting a key.

Passwords remain machine-specific. Deleting a machine does not delete a shared SSH key.

Herdr and tmux: the remote session can continue while Sherpa disconnects. Sherpa can reattach when you return, provided that session still exists.

SSH terminal: tabs belong to the live SSH connection. Navigation within the foreground app keeps them open, but disconnecting, losing connectivity, or app suspension ends the attachment. A retained screen is not a restored shell; open a new shell to continue.

Leaving the workspace detaches the attachment. Explicitly closing a tab closes that remote tmux window and its processes after confirmation. Tmux's existing pane layouts and sizing policies still apply.

Sherpa uses the history mechanism appropriate to each mode: Herdr's server-owned viewport, tmux copy mode, or local scrollback for ordinary SSH. Use the keyboard toolbar for Page up/down and the floating button to jump back.

A full-screen application can have its own internal scroll position. Auto-hiding the button at the bottom of an agent conversation is not available for every application. Customized tmux bindings or agent keybindings can also change scrolling behavior.

Try changing tabs and returning, then check that you're on the latest app version. If it continues, email the server mode, remote program, device orientation, and screenshots before and after the keyboard transition. Avoid sharing sensitive terminal content.

Check that the selected backend is installed and available in non-interactive SSH sessions. For Herdr, you can set an explicit executable path in the machine settings. Tmux mode searches the remote PATH and common user/Homebrew installation directories. Sherpa does not silently switch server modes when a backend is unavailable.

The current app automatically accepts server host keys, including changed keys, and records the latest key. That is not strict host-key pinning. Use trusted server addresses and network paths; do not treat a successful connection as independent verification of a server's identity.

Disconnect and remove machines in Machines, then delete unused shared keys in Keys. Do this before uninstalling if you want to remove credentials: Keychain entries can survive app removal. Deleting local records does not delete remote sessions, files, server logs, or OS backups. See the privacy policy for details.

Sherpa is planned as a $5.99 USD one-time App Store purchase, with local equivalent prices. There is no subscription or separate Pro unlock. Apple handles purchase records, redownloads, and refund eligibility. Use Apple's Report a Problem service for refund requests.