Start with your installation
OmniTerm combines core terminal and file workflows with optional remote-access, sharing and automation tools. A guide explains a feature when it is available; it does not promise that every release includes every tool.
Availability depends on the application release, device capabilities, selected route, and service or organization policy. Signing in or changing a plan does not install a missing capability.
Common differences
| Workflow | What to check |
|---|---|
| Direct SSH on a native device | The device can reach the server and has valid SSH credentials. An OmniTerm account is not required for the direct connection itself. |
| Browser terminal | A configured Gateway or compatible relay route is required; a browser does not open an ordinary local SSH socket. |
| SFTP | The server supports SFTP and your account can access the files. |
| Local forwarding or SOCKS5 listener | A supported native app is required. A browser cannot bind a TCP listener on your device. |
| Remote desktops and X11 | The platform, remote service and route must all support the feature. |
| Managed relay, cloud workspace or connected assistants | Completed account sign-in and the enabled service are required for the hosted managed workflow. |
| Agent tasks, teams and integrations | The relevant tool, permissions and dependencies must be configured. |
When a control is missing
Check the app version, route and account. A hidden or unavailable option may be intentional. Do not disable certificate checks or use someone else's credentials to force it to appear.
Advanced transports are not interchangeable: a sharing transport is not automatically an SSH or file-transfer route. Read transport selection before allowing fallback. For a planned rollout, test the actual device and workflow combinations you need. These guides do not imply universal cross-platform certification.
MoQ and an application VPN workflow are not available in the current app. Native local project-file and Git automation requires the supported Linux agent environment. The hosted cloud workspace does not have a general offline-mode switch.
See troubleshooting for the information to include when requesting help.