OrgBots

Install OrgBots from its signed APT archive.

Download the installer, read it, then run it in Bash. It checks the signing key fingerprint before adding the repository and installing the package.

Before you start

These instructions support Ubuntu 24.04 on amd64. You need an internet connection and permission to use sudo. Install the stated prerequisites if they are missing:

sudo apt update
sudo apt install curl ca-certificates gnupg coreutils

The installer does not automatically install missing prerequisites. APT shows its normal package confirmation prompt before installation.

Download, inspect, and run

Keep the commands separate. First download the script:

curl -fL https://raw.githubusercontent.com/acememe7/Orgbot/main/scripts/install-orgbots.sh -o install-orgbots.sh

Read the downloaded file and confirm its source before you run it:

less install-orgbots.sh

Then run it as your user. It requests elevated access only for system package configuration:

bash install-orgbots.sh

Open OrgBots and connect a provider

Launch OrgBots from the desktop menu or run orgbots in a terminal. In Accounts, add an API provider key or use a supported CLI sign-in already set up on this computer. API credentials and provider subscriptions are separate billing arrangements. Configure a local or reachable Ollama endpoint if you use Ollama.

Upgrade OrgBots

After the one-time repository setup, use APT to refresh package information and install updates:

sudo apt update
sudo apt install orgbots

The current package is OrgBots 2.0.0. The APT archive is a third-party repository hosted at the OrgBots GitHub Pages archive, separate from Ubuntu's built-in archive.

Remove OrgBots

Remove the application through the package manager:

sudo apt remove orgbots

This does not automatically remove the repository configuration or your user data. You can leave the source configured for future installation or remove its source and keyring files after inspecting them.

Workspace protection requirements

OrgBots does not format or configure disks. Applying a replacement or removal requires a writable ext4 drive mounted at /mnt/hdd. Originals are preserved under /mnt/hdd/OrgBots Trash. If the drive is unavailable or fails verification, protected integration stops.

Local workspace protection does not provide complete network or credential isolation. Private portable backups are unencrypted and limited to 64 MiB. Treat secrets pasted into agent history as sensitive. Read the workspace safety guide before connecting providers.

Need help?

Email theaece@theaecestudio.com or review the installation source guide.