Know where input goes
An active terminal sends your input to the selected remote session. The shell, permissions and commands belong to that remote machine. A terminal tab is not a separate safety boundary: a command can make lasting changes wherever that account has permission.
Before a sensitive action, check the host, username and active pane. A familiar prompt is helpful, but it does not replace the original host identity check.
Use the terminal controls
- Open a connected host and select Terminal.
- Select the intended pane before typing. Click or tap the terminal to give it focus.
- Use the terminal's Copy terminal or Paste terminal controls when operating-system shortcuts conflict with the remote application.
- Review any paste warning before sending multiline or potentially dangerous input.
- Open SFTP Files for file browsing instead of treating a pasted local path as a remote upload.
Keyboard handling can differ between desktop, browser and mobile clients. A browser or operating system may reserve a shortcut before OmniTerm receives it. See settings and shortcuts for customization.
Disconnection and history
Scrollback is a view of received output, not proof that a process is still running. When the connection badge reports an error, open Connection Details before retrying. Avoid typing while disconnected because some workflows can queue input for reconnection.
A persistent remote shell can outlive its current connection when the server and session support it. Learn the difference between reconnecting and restarting in workspaces and sessions.
For images and files, use clipboard attachments; copying text alone does not transfer a file.