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, OmniTerm can use a remote terminal multiplexer such as tmux to keep a shell separate from the current network connection. 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.
See Live Share for collaboration and troubleshooting for reconnection problems.