GlinkBot documentation

Linux desktop

Install GlinkBot on Linux, configure its browser and understand local computer control.

Download and install

Get available Linux x64 packages from the GlinkBot download page. Installed desktop packages include the application server and browser runtime; Node.js and pnpm are not required to run them. Use the Debian package on Ubuntu 24.04 LTS for system dependencies and browser sandbox configuration.

From the folder containing your download, install the actual filename shown on the download page:

sudo apt install ./GlinkBot-<version>-amd64.deb

Replace <version> with the downloaded version. Then open GlinkBot from your application launcher. For a portable AppImage, make the downloaded file executable and launch it:

chmod +x ./GlinkBot-<version>-x86_64.AppImage
./GlinkBot-<version>-x86_64.AppImage

The desktop app is free. Model providers and external hosting can charge separately.

Updates and removal

Automatic updating is supported for the Linux DEB when a compatible GlinkBot update feed is published. A newly built package does not automatically activate an update feed. Installation may require a system password prompt. AppImage users should download and replace their application manually.

To uninstall a Debian installation:

sudo apt remove glinkbot

Uninstalling the package does not erase your conversations. Back up ~/.glinkbot before changing or deleting application data. Window preferences normally live in ~/.config/glinkbot.

Computer access

A screen preview does not grant control. On GNOME Xorg, enable local control explicitly and assign the bot to This computer. Tool permissions and approvals still apply. Standard Wayland sessions keep local control disabled where safe input isolation is unavailable; a portal-based screen preview may still be available. Do not bypass the safety gate.

For a separate desktop, use Private desktops or your own Linux server. The app must keep running on the host that executes your agents.

Bundled bot browser on Ubuntu 24.04

The DEB configures an AppArmor rule for its package-owned browser executable while keeping the browser sandbox enabled. Upgrades refresh the rule and removing the package removes it. Browser use and approval settings remain your choice.

An AppImage cannot install system policy. On hosts restricting unprivileged user namespaces, its bundled browser may report No usable sandbox. Use the DEB instead. Do not launch with --no-sandbox or disable AppArmor globally.

Arch Linux and EndeavourOS

These distributions are not the primary GlinkBot packaging target. The x64 AppImage may work with the required desktop libraries; compatibility depends on your distribution. No native pacman package or automatic AppImage update is promised by GlinkBot.

Omarchy (Hyprland, experimental)

Local control on Hyprland requires the compatible Cua plugin and driver, not just a Wayland session. This support is experimental. Install the distribution's cua-driver-bin and cua-hyprland-plugin packages and configure the plugin using Cua's Omarchy guide.

Check the plugin status:

hyprctl -j cua:status

GlinkBot checks that the plugin is configured, its input transport is ready, and its ABI matches the compositor. If the checks pass, choose Enable local control (Beta), wait for Ready, and assign the bot to This computer. A missing or incompatible plugin keeps control disabled. Use Try again after correcting the installation.

Agent command-line tools

A graphical launcher may not inherit your terminal's PATH. Restart GlinkBot after installing an agent CLI or signing in to its provider. If needed, launch with an explicit extra tool directory:

OMB_EXTRA_PATH=/your/custom/bin ./GlinkBot-<version>-x86_64.AppImage

Provider sign-in is separate from a GlinkBot account: GlinkBot does not require or offer a hosted account sign-in. For startup problems, see troubleshooting and logs.

GlinkBot documentation, reviewed for the 0.0.4 codebase. Public download availability can differ. Licenses and acknowledgments.