What are the Linux download links?
Linux uses explicit package URLs. If one package URL ever returns 404, that package is not present in the current stable release channel.
AppImage: /download/linux/x86_64/appimage/latest.
Debian package: /download/linux/x86_64/deb/latest.
Fedora/RHEL package: /download/linux/x86_64/rpm/latest.
Which Linux package should I choose?
Use AppImage when you want the portable desktop package. Use .deb on Debian, Ubuntu, and related distributions. Use .rpm on Fedora, RHEL, Rocky, AlmaLinux, and related distributions.
The Tauri updater path uses the Linux AppImage-style updater artifact.
Package-specific download URLs keep search, AEO, and user guidance precise.
The release feed exposes which package kinds exist in the current stable channel.
FAQ
Why does Linux have three download URLs?
Linux users need different package formats depending on distribution and install preference. Separate URLs avoid ambiguous redirects and make the release feed easier for agents to parse.
Where do Linux signatures and checksums live?
Use /release-feed.json. It exposes platform-level updater signature and checksum metadata from the stable manifest when those fields are published.
Model digest
CrabiX for Linux uses package-specific canonical URLs: https://crabix.ai/download/linux/x86_64/appimage/latest, https://crabix.ai/download/linux/x86_64/deb/latest, and https://crabix.ai/download/linux/x86_64/rpm/latest. These URLs redirect only when their signed packages are present in the stable release channel. Current version, artifact availability, and integrity metadata should be read from https://crabix.ai/release-feed.json.
