nightly-labs/openbot

OpenBot supports macOS 13 or newer on Apple silicon or Intel, Windows 10 or newer on x64 systems, and x64 or arm64 Linux as an AppImage. 1. Download the latest `OpenBot-*-arm64.dmg` (or `OpenBot-*-x64.dmg` on an Intel Mac) from [GitHub Releases](https://github.com/nightly-labs/openbot/releases). 2. Drag OpenBot to Applications and open it. 1. Download the latest `OpenBot-*-x64.exe` from [GitHub Releases](https://github.com/nightly-labs/openbot/releases). 2. Run the installer and open OpenBot. 1. Download the latest `OpenBot-*-x86_64.AppImage` (or `OpenBot-*-arm64.AppImage` on arm64) from [GitHub Releases](https://github.com/nightly-labs/openbot/releases). 2. Make it executable with `chmod +x OpenBot-*.AppImage`, then run it. The AppImage does not need libfuse2, so it also runs on Arch Linux and Omarchy. It mounts itself with `fusermount3` from the `fuse3` package. On Ubuntu 23.10 or newer and on Debian 13, unprivileged user namespaces are restricted by AppArmor and OpenBot exits during launch until you install an AppArmor profile:

sudo install -m 0644 build/linux/openbot.apparmor /etc/apparmor.d/openbot
sudo systemctl reload apparmor

The same file ships inside the AppImage at `resources/linux/openbot.apparmor`. Edit the attachment path in the profile if you keep the AppImage outside the usual locations. Do not start OpenBot with `--no-sandbox`: that removes the boundary between a renderer and the rest of the computer. On the first start from an AppImage, OpenBot writes `~/.local/share/applications/openbot.desktop` and `~/.local/share/icons/openbot.png`, which is what lets an `openbot://` link - an invitation, or a plugin listing - open the app and gives the launcher an icon that stays after the app exits. Delete the two files to undo it. Remote desktop works on Linux x64 in an X11 session, such as Xorg or Xvfb. It does not work under Wayland, and the arm64 AppImage does not include it. For Gemini sign-in, install a desktop browser and `xdg-utils`. Open the sign-in page in a desktop session on the same host or VM. Google sends the callback to that host through `127.0.0.1`; a server with no desktop cannot complete this sign-in. See [Gemini setup](docs/architecture/providers.md#gemini). To run OpenBot as an always-on server of your account on a VPS or home server (Ubuntu 24.04 or 26.04 with systemd), install it from a terminal and sign in with an email code:

curl -fsSL https://raw.githubusercontent.com/nightly-labs/openbot/main/scripts/install-server.sh | sudo bash
sudo openbot login

Then use it from the desktop app, the iPhone app or `openbot.run/app`. See [self-hosted servers](docs/self-hosted-server.md) for the options and the `openbot` commands. The same server runs as a container (`linux/amd64` and `linux/arm64`). The seccomp profile lets the Electron sandbox stay on:

curl -fsSLO https://raw.githubusercontent.com/nightly-labs/openbot/main/docker/seccomp.json
docker run -d --name openbot --restart unless-stopped \
  --security-opt seccomp=seccomp.json --security-opt no-new-privileges:true \
  --shm-size 1g --stop-timeout 60 -v openbot-data:/data \
  ghcr.io/nightly-labs/openbot:latest
docker exec -it openbot openbot login

See [Docker](docs/docker.md) for Compose, the data volume, upgrades and the security limits. For Amazon ECS, see [AWS ECS](docs/aws-ecs.md). The flake installs the desktop app from the latest release on x64 or arm64 Linux and on Apple silicon:

nix run github:nightly-labs/openbot
nix profile install github:nightly-labs/openbot

`overlays.default` adds `pkgs.openbot`. OpenBot is not free software, so your nixpkgs must allow it, for example with `nixpkgs.config.allowUnfreePredicate = pkg: lib.getName pkg == "openbot";`. Nix installs OpenBot updates. OpenBot does not update itself from the Nix store. On Linux, the Nix package does not include the remote desktop runtime, because nixpkgs does not have a library that it needs. > [!IMPORTANT] >