Arrange your work
A workspace brings sessions and tools together. Use tabs and supported split layouts to keep related terminals visible, such as an application shell beside its logs. Saved workspace arrangements are different from the processes running on the remote servers.
- Open the hosts you need and switch to the workspace.
- Use its layout or split controls to arrange sessions.
- Select a pane before typing; verify its host and account.
- Save a layout or template where that option is available.
- When reopening a workspace, confirm the session state rather than assuming every old connection resumed.
What a persistent session means
On a compatible server, LeapTerm can attach an SSH shell to tmux to keep it separate from the current network connection. Enable Attach to Tmux session in the SSH host settings where supported; it is off by default. Reattaching reconnects you to that remote session instead of necessarily starting the command again.
Persistence depends on the remote multiplexer being installed and usable, the account retaining access, and the server and processes remaining alive. It does not protect against a server reboot, an administrator stopping the process, or resource exhaustion.
Reconnect safely
After an interruption, check the connection status and reattach to the intended session where supported. Inspect the remote state before repeating a command: a deployment or file operation may have completed while the connection was down.
Closing a tab, ending a share, revoking access and terminating a remote process are different actions. Do not use a disconnected viewer as proof that a background job stopped. For a task that must be stopped, verify its state on the remote machine through an authorized connection.
Cross-device continuity
Workspace continuation uses an independently enrolled leap-agent on the target and a supported installed app trusted for that agent. The saved protected session's original runtime must still be available. Ordinary SSH and tmux reconnection are separate from the protected Continue workflow.
- Open Recover workspace sessions in the workspace and unlock recovery or the vault when prompted.
- For another device, configure Cloud sync settings and enable Sync this workspace across devices. Review the included content in Sync this workspace?, then choose Approve workspace sync. Wait for Saved to cloud (encrypted).
- On the destination, use the same account and independently verified enrollment for the original agent. Select the saved pane and choose View here to inspect it or Continue here to request control. Recover on this device also reattaches for viewing.
- Check the recovery result and current display. Wait for input permission before typing.
Workspace sync carries saved layout and session references and retains local editor drafts with their original file contents in encrypted workspace records. Remote files change only through an explicit Save action. Each device still needs its own trusted agent access. Follow active device switches the selected pane and does not itself transfer input control. If the app reports Trusted app required, continue in an enrolled installed app.
For an agent-backed in-app browser, Continue from here reattaches to the original live page, with its current DOM and form state, when the matching agent runtime and page remain available. A saved address or checkpoint cannot recreate that live state after the page ends. If recovery reports that the original session or page is unavailable, inspect the remote state and explicitly open a new session or page when needed.
See Live Share for collaboration and troubleshooting for reconnection problems.