Get the right application
Start with the official LeapTerm website and its release or access instructions. Availability is release-specific: a platform listed in a preview does not mean a public package is available for it today. Choose the package for both your operating system and processor.
Desktop bundles may contain supporting files next to the application. Extract and keep the complete bundle, not just the executable. A relay kit is a server component, not the LeapTerm application. For iPhone and iPad, use the approved distribution channel named for that release. Do not disable operating-system trust checks to install an unknown package.
Match the release package
The current release packaging distinguishes the desktop application from the background agent:
| Application | Package to look for in the selected release |
|---|---|
| macOS Apple Silicon | Application ZIP for macOS 13.5 or later. Do not assume an Intel build is included. |
| Linux | Desktop bundle for Ubuntu 24.04 x64, distributed as a complete archive. |
| Windows x64 | Portable ZIP; extract the whole application and its libraries. It is not an MSI installer. |
| Android | The APK appropriate to your device, or the universal APK, when supplied. |
| iPhone and iPad | The approved Apple distribution channel for that release; an internal build is not proof of store availability. |
| Browser | The administrator's configured web app. Web archives are deployment packages for its operator; users follow the release's access instructions. |
Linux agent .deb and .rpm packages install the background agent, not the desktop application. Only use packages actually supplied for your release.
When a release supplies the strict browser client, use its matched browser package and native host and complete the release's activation instructions. It requires an independently verified enrolled agent and owner approval of your exact local device key. Installing the package or signing in does not complete that enrollment. See features and availability.
Update a native installation
Your distribution determines the update path. Configured Windows installations and Linux AppImages use Velopack; direct macOS applications use Sparkle. Store or package-manager installations use their original distribution channel. Portable archives can require manual installation or migration.
The update service supplies version and verification metadata. Managed native update packages come from download.leapterm.com; manual downloads can use the selected release's official GitHub assets. Follow the release's verified download path before installing a package.
- Finish or safely pause your work. Check your backup and recovery material before replacing an installation.
- Open Application updates and check the version and build offered for your platform.
- With a configured native updater, follow its update dialog or choose Download, then Restart to Apply when offered.
- For a manual package, choose Download and verify, then Open verified package when those controls are offered. If you use Open download, authenticate the package using the selected release's verification instructions before installing it. Close the app when required and follow that release's installation steps.
- Reopen LeapTerm and confirm your version and saved connections. Use Check installed version when offered after a manual installation.
Open download starts the download workflow. Downloaded or verified packages and an installer handoff do not confirm that an update was installed. A failed check means update status is unknown. If startup verification reports recovery is required, follow the displayed recovery instructions or use the original distribution channel.
Manage a background agent
When your release supplies agent management for a Linux or macOS SSH server, connect to the intended server and open Omni Agent. A system installation requires administrator access. If installation controls are unavailable for that connection, use the release's supported installation instructions.
- Review Installed Version and Latest Release. Choose Install Agent, Upgrade Agent or Reinstall / Configure when offered.
- Check the exact version and whether the confirmation installs for this account or all users. The app verifies the complete signed runtime for that version before staging and installing it on the server. Reinstallation retains enrollment and task data.
- Wait for the operation result, then use Check Again to confirm the installed version. If the connection is lost or completion cannot be confirmed, inspect the server before retrying.
- Use Check Service to check the managed service. A service in standby can still need relay enrollment; service status does not establish relay connectivity or delegated access readiness.
Uninstall Agent removes the selected service and installed program while retaining enrollment and task data. For an agent supplied through Homebrew, Chocolatey or another package manager, follow that release's package-manager update and removal instructions. Windows agents use the release's signed platform package instructions; the native install and managed service activation workflow above is for Linux and macOS.
Protect your data
Portable desktop packages and sideloaded Android packages can require manual installation. Do not uninstall Android before upgrading unless you intend to remove local data. A browser deployment is updated by its administrator; reload after the administrator confirms deployment.
Keep recovery material separately. An older application may not understand data written by a newer release, so retaining an old executable is not a complete rollback plan.