Windows CI / windows ([bun run --cwd packages/app-core test bun run --cwd packages/elizaos test bun run --cwd packages/cloud/shared test], app-and-cli) (push) Waiting to run
Windows CI / windows ([bun run --cwd packages/scenario-runner test bun run --cwd packages/vault test bun run --cwd packages/security test bun run --cwd plugins/plugin-coding-tools test], framework-packages) (push) Waiting to run
Windows CI / windows ([bun run --cwd plugins/plugin-elizacloud test bun run --cwd plugins/plugin-discord test bun run --cwd plugins/plugin-anthropic test bun run --cwd plugins/plugin-openai test bun run --cwd plugins/plugin-app-control test bun run --cwd plugins/pl… (push) Waiting to run
Windows CI / windows ([node packages/scripts/run-turbo.mjs run build --filter=@elizaos/core --filter=@elizaos/shared --filter=@elizaos/agent --concurrency=4 node packages/scripts/run-bash-linux-only.mjs scripts/verify-riscv64-buildpaths.sh node packages/scripts/run… (push) Waiting to run
Windows CI / windows ([node packages/scripts/run-turbo.mjs run typecheck --filter=@elizaos/core --filter=@elizaos/shared --filter=@elizaos/cloud-shared --concurrency=4 bun run --cwd packages/core test bun run --cwd packages/shared test], core-runtime, 75) (push) Waiting to run
The elizaOS distribution. The canonical Linux build is the Tails-derived
elizaOS Debian fork under linux/; Android lives under android/ as the
separate AOSP fork.
The active Linux build ships directly under linux/: one multi-arch
live-build selected via ELIZAOS_ARCH. It is the canonical elizaOS Debian
fork. There are no distro variants in this repo; amd64/arm64/riscv64 are
architecture targets of the same build.
The upstream-derived source remains in linux/tails/ because inherited
Tails live-OS plumbing, AppArmor policy, Greeter code, Persistent Storage,
and update hooks key off those names. Product identity is elizaOS; Tails
references are retained only for provenance, licenses, and internal plumbing.
The Android side targets a curated list of devices where AOSP can be flashed
safely. Flash manifests under android/installer/manifests/ enumerate the
supported devices; OS release manifests carry a channel
(alpha / beta / stable / nightly, validated in scripts/os-release-lib.mjs).
Building locally
Building a live image requires Docker run with --privileged (live-build needs
binfmt_misc and loop devices). See linux/README.md for prerequisites and the
step-by-step build flow.
Flashing
The USB flasher under usb-installer/ handles target selection, format, write, and verify in one pass. It's destructive — requires explicit confirmation of the target block device.
User-facing docs
Engineering notes for this package live in docs/ (TEE plan, CI/CD production plan, release plan, apt repo). Per-subsystem README files: linux/README.md, android/README.md, usb-installer/README.md.