Download AgentUX

Try the live ISO first, or install directly. Both come for x86_64 PCs and 64-bit ARM UEFI machines, and install the same signed image.

These are the newest release, from iso/stable/ on download.agentuxos.org. Every release is kept on GitHub releases.

Live ISO

Boots the real desktop from RAM without touching the disk, with a demo of fake agents already running in the cockpit, so nothing is billed.

When you want to keep it, Install AgentUX on the desktop installs the signed image from the registry. Installing needs an internet connection.

Installer ISO

Goes straight to the installer: pick the disk, language and time zone, and create your account. The image is on the ISO, so it installs offline.

It is built with bootc-image-builder and still looks like Fedora’s installer.

Both boot with UEFI only, no legacy BIOS. In a VM, give AgentUX at least 4 GB of RAM; 8 GB is comfortable. The aarch64 ISOs target UEFI machines Fedora supports (SystemReady hardware, VMs on Apple silicon or Ampere hosts); boards that need their own firmware or kernel are not covered.

Check the download

Next to every ISO are its .sha256 and a cosign signature of that checksum, made with the key that signs the images. The public key is agentux-os.pub in agentux-os, and /etc/pki/containers/agentux-os.pub on an installed system.

1. Check the checksum

curl -LO https://download.agentuxos.org/iso/stable/agentux-live-x86_64.iso.sha256
sha256sum --check agentux-live-x86_64.iso.sha256

2. Check that the checksum is signed

curl -LO https://download.agentuxos.org/iso/stable/agentux-live-x86_64.iso.sha256.sigstore.json
curl -LO https://raw.githubusercontent.com/agentux-os/agentux-os/main/files/etc/pki/containers/agentux-os.pub
cosign verify-blob --key agentux-os.pub \
  --bundle agentux-live-x86_64.iso.sha256.sigstore.json \
  agentux-live-x86_64.iso.sha256

3. Write it to a USB stick

# replace /dev/sdX with the stick; everything on it is erased
sudo dd if=agentux-live-x86_64.iso of=/dev/sdX bs=4M status=progress oflag=sync

Use the same names with the ISO you downloaded. A release directory also has a combined, signed SHA256SUMS; see Downloads in agentux-os.

Release channels

An installed system follows exactly one channel and updates from it with bootc upgrade. You can change channel at any time.

:stable

Releases. It moves only when a v* tag has passed every test, including the ISO installs, and the maintainer approves it. Systems installed from these ISOs follow :stable.

:latest

Nightly builds of main, rebuilt every day for Fedora's updates and on every merge. Newer, less tested. Systems installed before the first release follow it until you switch.

Each release also keeps its own tag (:v<version>) and each nightly a dated one (:<YYYYMMDD>); neither ever moves. Going from :latest to :stable usually means an older image, which is fine on an image-based system.

Already on Fedora Atomic?

Any Fedora Atomic or bootc system can switch to AgentUX in place, on x86_64 and aarch64 alike: each tag is a multi-arch manifest, and bootc pulls the image for your machine. Your home directory is untouched.

KDE Plasma (the default)

sudo bootc switch ghcr.io/agentux-os/agentux:stable
systemctl reboot

Hyprland

sudo bootc switch ghcr.io/agentux-os/agentux-hyprland:stable
systemctl reboot

The Hyprland image adds a tiling session laid out for watching several agents, and keeps Plasma one click away at login. Release ISOs are Plasma only, so install one and switch. Use :latest instead of :stable for nightly builds. If an update breaks something, sudo bootc rollback (or the previous entry in the boot menu) brings back the image you had.

Check the image signature

cosign verify --key agentux-os.pub ghcr.io/agentux-os/agentux:stable

cosign verify ghcr.io/agentux-os/agentux:stable \
  --certificate-identity-regexp '^https://github\.com/agentux-os/agentux-os/\.github/workflows/build\.yml@refs/tags/v' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

You do not need this on an installed system: its container policy requires the AgentUX key signature, so bootc upgrade and bootc switch refuse an unsigned image before downloading it.

After the first boot

The agent CLIs install themselves on your first login. Then sign in to each vendor CLI you want to use, open the cockpit with Meta+A, and start a run. Getting started walks through it.