Download · Linux

Download CrabiX for Linux

Linux downloads are package-specific so users and agents do not guess the wrong format. Use AppImage for a portable desktop build, Debian package for Debian/Ubuntu-style systems, and RPM for Fedora/RHEL-style systems. Current availability and integrity metadata are reported by the release feed.

Author: CrabiX · Published: 2026-06-13 · Last updated: 2026-06-30

What should you remember?

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.

Markdown: /download/linux.md · Agent feed: /agent-feed.json