# Install Lolly Lolly runs in a browser with nothing to install, and it also ships as a real app for the machine in front of you. This page is the one list of every packaged build: what each one is, how to install it, and how to check you got the file we made. The current main web shell requires WebGPU. See [supported environments](/info/start/supported-environments.html) for the tested browser versions and the separate native qualification status. A web-only update does not replace the packaged downloads below. The app is the same either way. Same tools, same brand packs, same files out - on the web, macOS, Windows, Linux, iOS and Android, plus the [CLI](/info/build/cli.html) and the terminal [TUI](/info/build/tui.html). Install it, open a hosted address, or run both at once. The packaged builds add native file dialogs, a home in your application menu and a copy that keeps working with the network unplugged. > **Direct downloads are live.** Every packaged build below links straight to the > file on `lolli.li`. Each platform has a stable `lolly-latest.*` link that always > points at the newest build, alongside versioned files that never change. Signed > system repositories (openSUSE OBS, Flathub) are planned and will land here when > they do; until then these direct files - and the build-it-yourself route in each > section - are the way in. Prefer no install at all? Use [the web app](/); it > needs no install and is the same application. --- ## macOS **Apple silicon (M1 and later) and Intel, `.dmg`.** Version 1.0.9 requires macOS 13.5 or later, including its bundled terminal tools. Download the disk image, open it, and drag Lolly to Applications. Nothing else is needed - the app carries its own engine and tool catalogue. - **Apple silicon:** [`lolly-latest.dmg`](https://lolli.li/lolly-latest.dmg) - always the newest build. - **Intel:** [`lolly-latest-x64.dmg`](https://lolli.li/lolly-latest-x64.dmg) - always the newest build. - **Versioned:** `https://lolli.li/Lolly__aarch64.dmg` and `https://lolli.li/Lolly__x64.dmg` - pinned, never overwritten. Build it yourself: ```bash git clone https://github.com/lolly-tools/lolly.git cd lolly && pnpm install pnpm -C shells/tauri-desktop install --frozen-lockfile ``` Configure catalog signing as described in the Build Guide, then build: ```bash LOLLY_PROFILE=lolly-start LOLLY_EMBED_CATALOG=profile pnpm run build:desktop ``` The app is written to `shells/tauri-desktop/src-tauri/target/release/bundle/macos/`. Full prerequisites are in the [Build Guide](/info/build/build-guide.html). --- ## Tumbleweed **openSUSE Tumbleweed, `.rpm`, x86_64.** ```bash sudo zypper install https://lolli.li/lolly-latest.rpm ``` Or download [`lolly-latest.rpm`](https://lolli.li/lolly-latest.rpm) and install the file directly. The versioned build sits beside it, for example `https://lolli.li/lolly-desktop--0.x86_64.rpm`. A signed OBS repository - so updates arrive with the rest of your system - is planned; until it is live a direct `.rpm` does not auto-update, so check back here for a newer build. The package build itself is described in `shells/tauri-desktop/rpm/README.md`. --- ## Leap **openSUSE Leap 16, `.rpm`, x86_64.** ```bash sudo zypper install https://lolli.li/lolly-latest-leap16.rpm ``` Leap 16 has its own build, and you need it: the Tumbleweed `.rpm` (`lolly-latest.rpm`) is compiled against a newer glibc and refuses to install here with `nothing provides 'libm.so.6(GLIBC_2.43)'`. The versioned build sits beside the alias, for example `https://lolli.li/lolly-desktop--0.leap16.x86_64.rpm`. The two packages are otherwise identical in content; only the toolchain they were built against differs. **Leap 15.6 is not a target.** The dependency tree needs Rust 1.88 or newer and 15.6's default toolchain is older, so supporting it would mean pinning a second Rust toolchain into the project and maintaining two build stories. Tumbleweed ships 1.97.1 and Leap 16 is current; those two are the supported pair. On 15.6, use the Flatpak below. --- ## Flatpak **Any Linux distribution, `.flatpak`.** The Flatpak is the right choice on Fedora, Debian, Ubuntu, Arch, Leap 15.6, an immutable desktop, or anything else that is not one of the two RPM targets. It brings its own runtime, so it does not care what your distribution ships. Download the single-file bundle and install it: ```bash curl -LO https://lolli.li/lolly-latest.flatpak flatpak install --user ./lolly-latest.flatpak flatpak run tools.lolly.Desktop ``` The app id is `tools.lolly.Desktop` and the runtime is `org.gnome.Platform` version 50. A Flathub listing - which would carry updates automatically - is planned; the manifest and the local build steps are in `shells/tauri-desktop/flatpak/README.md`. --- ## Arch **Arch and its derivatives, from the Lolly pacman repository.** Add the repository to `/etc/pacman.conf`: ```ini [lolly] SigLevel = Optional TrustAll Server = https://lolli.li/arch/$arch ``` then install - and from here on, update - with pacman itself: ```bash sudo pacman -Syu lolly-desktop-bin ``` The `SigLevel` line is needed because the repository is not yet GPG-signed; it scopes the exception to this one repository only. An AUR package under the same name is planned once AUR account registration reopens; the recipe is maintained in `shells/tauri-desktop/linux/arch/`, and you can build it by hand today: ```bash git clone https://github.com/lolly-tools/lolly.git cd lolly/shells/tauri-desktop/linux/arch && makepkg -si ``` The package repacks the official desktop version pinned in its recipe and installs the whole desktop integration - the `.lolly` MIME type, `lolly://` links, the thumbnailer, the GNOME Shell search provider, the D-Bus services, and the KDE service menu. On Hyprland and other wlroots compositors the colour picker and the wallpaper feature go through the desktop portal, so an `xdg-desktop-portal` backend must be running (Hyprland ships its own); the desktop search integration is a GNOME/KDE feature. --- ## Debian / Ubuntu **Debian, Ubuntu and derivatives, `.deb`.** Pick the build for your architecture and install it with `apt`: - **amd64 (Intel/AMD):** [`lolly-latest.deb`](https://lolli.li/lolly-latest.deb) - **arm64 (ARM servers, Raspberry Pi, ARM VMs):** [`lolly-latest-arm64.deb`](https://lolli.li/lolly-latest-arm64.deb) For amd64: ```bash curl -LO https://lolli.li/lolly-latest.deb && sudo apt install ./lolly-latest.deb ``` For arm64: ```bash curl -LO https://lolli.li/lolly-latest-arm64.deb && sudo apt install ./lolly-latest-arm64.deb ``` Versioned files sit beside them, for example `https://lolli.li/lolly-desktop-_amd64.deb` and `lolly-desktop-_arm64.deb`. A direct `.deb` does not auto-update, so check back here for a newer build, or use the Flatpak above, which updates in place once its Flathub listing is live. --- ## Android **Phone and tablet, `.apk`, installed directly.** No store account, and no store. Download the APK, open it, and allow your browser or file manager to install applications this once. Android will ask - that prompt is the system working correctly, not a warning about this file. - **Download:** [`lolly-latest.apk`](https://lolli.li/lolly-latest.apk) - always the newest build. - **Versioned:** `https://lolli.li/Lolly-.apk`. - **Minimum:** Android 7.0 - **Architecture:** `arm64-v8a` Check the file before installing it. Every release publishes a checksums file at `https://lolli.li/SHA256SUMS.txt`: ```bash sha256sum lolly-latest.apk ``` Compare the result with the line for that filename. If they differ, do not install it. Build it yourself from `shells/tauri-mobile` with `pnpm run build:android`; the Android SDK and NDK prerequisites are in the [Build Guide](/info/build/build-guide.html). --- ## iPhone and iPad **iOS and iPadOS. No download yet.** An iPhone or iPad app has to be signed with an Apple developer identity before the device will install the file, so there is no download to hand out. Until there is, open [the web app](/) in Safari. It is the same application, and **Share, then Add to Home Screen** gives the web app an icon of its own. The web app needs WebGPU; [supported environments](/info/start/supported-environments.html) lists what has been tested so far. To build and sign the app yourself, see [Building for iOS](/info/build/ios-build.html). --- ## YunoHost **Your own server, as a YunoHost app.** On a [YunoHost](https://yunohost.org) server, install Lolly from its app package: ```bash sudo yunohost app install https://github.com/lolly-tools/lolly_ynh ``` The package serves the same web app from a domain of your own, with the same security headers as lolly.tools. It needs a whole domain, keeps nothing on the server, and fetches the on-device models from `lolli.li` the first time a tool asks for one. The [YunoHost section of the deployment guide](/info/operate/deployment.html#yunohost) covers what the package installs and how access to the app works. --- ## Everything else | Surface | How you get it | Notes | |---|---|---| | **Web** | [Open it](/) | Nothing to install. Add it to your home screen or dock and it keeps working with the network unplugged. | | **Windows** | [`lolly-latest.exe`](https://lolli.li/lolly-latest.exe) (NSIS installer) or [`lolly-latest.msi`](https://lolli.li/lolly-latest.msi) | x64. The installers are not code-signed yet, so Windows SmartScreen warns before the first run; compare the file with `SHA256SUMS.txt` (below) before you allow the install. Built by `pnpm run build:desktop` on Windows. | | **Linux, other** | [`lolly-latest.AppImage`](https://lolli.li/lolly-latest.AppImage) | x86_64. Falls out of the same desktop build: make the file executable and run the AppImage directly. For Debian/Ubuntu use the `.deb` above; the Flatpak is the supported cross-distro package. | | **Terminal** | `pnpm run cli` in a checkout | The same engine, headless. The desktop app carries the same CLI. See [the CLI guide](/info/build/cli.html#install). | | **Terminal, interactive** | `pnpm run tui` in a checkout | A full-screen terminal interface on the same engine. See [the TUI guide](/info/build/tui.html). | | **Tool-author SDK** | `npm i -D @lolly-tools/core` | Published on npm. The `HostV1` contract types, the manifest validator and a mock host for testing a tool without the app or a clone of the repository. See [Authoring Tools](/info/build/tool-publishing.html#try-it-without-the-monorepo). | | **Browser extension** | Load unpacked | See [Browser Extension](/info/create/extension.html). | | **Your own server** | Self-host the web shell | A static bundle behind any web server, including an air-gapped one. See [Deployment](/info/operate/deployment.html). | --- ## Checking what you downloaded Every release publishes a checksums file at [`https://lolli.li/SHA256SUMS.txt`](https://lolli.li/SHA256SUMS.txt). Put it next to your file, then: ```bash curl -LO https://lolli.li/SHA256SUMS.txt sha256sum --check --ignore-missing SHA256SUMS.txt ``` A line reading `OK` means the file on your disk is byte-for-byte the file the build produced. A `lolly-latest.*` file is a copy of the current versioned build, so it carries that build's hash - compare the value, not the name, if you kept the `latest` name. A mismatch means it changed somewhere between there and here, and the answer is always to download it again rather than to install it anyway. The files Lolly itself makes carry their own seal, which is a separate and stronger check - see [Verify It Yourself](/info/trust/verify-yourself.html). --- ## Which one should I pick? - **You are on a Mac.** The DMG for your chip: Apple silicon or Intel. - **You are on Windows.** The `.exe` installer. - **You are on Tumbleweed or Leap 16.** The RPM built for your distribution. - **You are on Arch.** The pacman repository. - **You are on any other Linux.** The Flatpak. - **You are on a phone.** The APK on Android; the web app on iPhone and iPad. - **You run a YunoHost server.** The YunoHost app. - **You do not want to install anything.** [The web app](/). It is the same application, and you can add it to your dock or home screen. - **You are rolling this out to other people.** Read [Deployment](/info/operate/deployment.html) first - it covers the three delivery postures and which package suits each one. --- Code ([MPL 2.0](https://www.mozilla.org/en-US/MPL/2.0/)) · Content ([CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/)) · [lolly.tools](https://lolly.tools)