|
| 1 | +# elizaOS Distribution Channels |
| 2 | + |
| 3 | +## Linux Desktop |
| 4 | + |
| 5 | +### Live USB (recommended for new users) |
| 6 | +- **ISO download**: Build via CI, flash to 8 GB+ USB with the USB installer app |
| 7 | +- **Debian package**: For installing elizaOS on an existing Debian/Ubuntu system |
| 8 | + |
| 9 | +### Virtual Machine |
| 10 | +- **OVA image**: Import into VirtualBox, VMware Fusion, or UTM (Mac) |
| 11 | +- **QCOW2 image**: For QEMU/KVM on Linux hosts |
| 12 | + |
| 13 | +## Android |
| 14 | + |
| 15 | +### elizaOS AOSP (full OS replacement) |
| 16 | +- **AOSP Flasher app**: GUI tool for Mac/Linux/Windows to flash your Pixel device |
| 17 | +- Supported devices: Pixel 9 Pro (caiman), others via community builds |
| 18 | +- Requires: USB debugging enabled, bootloader unlocked |
| 19 | + |
| 20 | +### elizaOS Android App (no AOSP required) |
| 21 | +- **APK sideload**: Install on any Android device without AOSP flashing |
| 22 | + |
| 23 | +## Install Tools |
| 24 | + |
| 25 | +### USB Installer |
| 26 | +Cross-platform app for creating elizaOS USB boot drives: |
| 27 | +- macOS: uses diskutil + dd with native authorization |
| 28 | +- Linux: uses lsblk + dd via pkexec |
| 29 | +- Windows: uses PowerShell disk management |
| 30 | + |
| 31 | +### AOSP Flasher |
| 32 | +Cross-platform GUI for flashing elizaOS AOSP onto Pixel devices: |
| 33 | +- Detects connected devices via ADB |
| 34 | +- Downloads elizaOS AOSP build artifacts |
| 35 | +- Guides through bootloader unlock + flashing |
| 36 | + |
| 37 | +## Release Channels |
| 38 | + |
| 39 | +| Channel | Cadence | Stability | |
| 40 | +|---------|---------|-----------| |
| 41 | +| `stable` | Major releases | Production-ready | |
| 42 | +| `beta` | Pre-release | Feature complete, may have bugs | |
| 43 | +| `nightly` | Daily automated builds | Latest, may break | |
| 44 | + |
| 45 | +## Generating homepage artifact data |
| 46 | + |
| 47 | +The OS artifact list shown on the homepage is generated from the release manifest at |
| 48 | +`packages/os/release/<date>/manifest.json`. To regenerate the data for a new manifest: |
| 49 | + |
| 50 | +```sh |
| 51 | +node packages/os/scripts/generate-os-homepage-data.mjs \ |
| 52 | + --manifest packages/os/release/beta-2026-05-16/manifest.json \ |
| 53 | + --output packages/os-homepage/src/generated/os-artifacts.ts |
| 54 | +``` |
| 55 | + |
| 56 | +The `write-homepage-release-data.mjs` script also reads the manifest directly at build |
| 57 | +time and merges manifest artifacts with the static artifact list before writing |
| 58 | +`packages/homepage/src/generated/release-data.ts`. |
0 commit comments