Start with your installation
LeapTerm 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 LeapTerm account is not required for the direct connection itself. |
| Browser terminal through a Gateway | An administrator-configured, admitted Gateway deployment with compatible protocol support is required. The Gateway is trusted with the protocol data and credentials it handles; review its trust boundary. A browser does not open an ordinary local SSH socket. |
| Strict browser client | When supplied for the release, install its matching isolated browser client and native host. Independently verify the enrolled agent and have its owner approve the exact local device key. Account sign-in or relay admission alone cannot grant access. |
| 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. |
| Interactive assistant views | The service must supply the separate hosted views, and your assistant host must support that delivery mode. Check the assistant integration requirements. |
| Managed full-device VPN | A release with the native VPN runtime, completed account sign-in, an available managed gateway and OS permission are required. A browser cannot install system routes or DNS. |
| Agent tasks, teams and integrations | The relevant tool, permissions and dependencies must be configured. |
| Native background-agent management | A supported Linux or macOS SSH server, a complete signed agent release and a connection with the installation controls are required. System installations need administrator access; use the release's package instructions for Windows. |
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.
Experimental MoQ is limited to compatible read-only browser broadcasts with a deployed provider that can confirm active-session cutoff. Check transport selection for its opt-in and service requirements.
When your release supplies it, Settings → Integrations → Managed full-device VPN reports platform support and any required OS setup. Connect VPN is offered on supported platforms; check the reported active status after connecting.
Native local project-file and Git automation requires a configured agent and working platform confinement. macOS and Windows also need the matching broker supplied and verified for the release. The hosted cloud workspace does not have a general offline-mode switch.
See troubleshooting for the information to include when requesting help.