Install Automexia#

Download Automexia v0.4.0 Public Alpha for Linux x64 or Arm64. Choose a package, verify it, and try it alongside your current terminal.

Choose your package#

Run uname -m: x86_64 means x64; aarch64 means Arm64. Download one package for your architecture.

Package	x64 / Intel and AMD	Arm64
Debian / Ubuntu	Download DEB	Download DEB
Fedora-family packaging	Download RPM	Download RPM
Portable archive	Download tar.gz	Download tar.gz

Windows, macOS, and AppImage packages are not available. This Alpha is for evaluation; review the Early Access limitations.

Requirements#

A GNU/Linux desktop session with working graphics and a local shell.
An x64 or Arm64 processor matching the package.
glibc, Fontconfig, FreeType, libgcc, and libstdc++. The DEB/RPM package manager resolves declared dependencies; portable packages need these libraries too.

Native build and package install/removal checks cover Ubuntu 22.04 on x64 and Arm64. RPM lifecycle checks ran on that Ubuntu runner; they do not establish full Fedora compatibility. Desktop, GPU, shell, and accessibility coverage vary. Portable archives are not static binaries or Alpine/musl packages. A headless SSH session alone cannot display the application. Do not launch it with sudo.

1. Verify before installing#

Save the package in a new download folder. Follow Release trust to verify the signed checksum list and your exact package. Stop if either check fails. Keep the files for one release together; do not mix versions.

2. Install one package#

Open your existing terminal in the folder containing the verified download.

Debian / Ubuntu#

For x64:

bash

sudo apt install ./automexia-terminal_0.4.0-1_amd64.deb

For Arm64:

bash

sudo apt install ./automexia-terminal_0.4.0-1_arm64.deb

Review the proposed changes before accepting. If dependencies cannot be resolved, stop rather than forcing installation.

Fedora-family systems#

For x64:

bash

sudo dnf install ./automexia-terminal-0.4.0-1.x86_64.rpm

For Arm64:

bash

sudo dnf install ./automexia-terminal-0.4.0-1.aarch64.rpm

The release uses Minisign and SHA-256 for verification. It does not configure an RPM signing-key repository. If your local policy rejects the package, stop and consult your administrator; do not disable signature checks or force dependencies.

Portable archive#

Create a new, empty directory. If this name already exists, choose another name instead of extracting over existing files.

bash

mkdir automexia-0.4.0-portable

For x64:

bash

tar -xzf automexia-terminal-0.4.0-x86_64-unknown-linux-gnu.tar.gz -C automexia-0.4.0-portable

For Arm64:

bash

tar -xzf automexia-terminal-0.4.0-aarch64-unknown-linux-gnu.tar.gz -C automexia-0.4.0-portable

Launch without elevation:

bash

./automexia-0.4.0-portable/automexia --version
./automexia-0.4.0-portable/automexia

Keep the executable, shell-integration folder, license, and notices together. Portable extraction does not register a desktop launcher or automatic updater.

3. Start Automexia#

For an installed DEB or RPM, use the Automexia Terminal desktop entry or run:

bash

automexia --version
automexia

The version output should include 0.4.0. Continue with Getting started. Keep a working terminal open during testing.

Updates and removal#

There is no automatic update channel configured by these packages. For each new release, read its notes, verify its files, close Automexia, and back up your configuration before installing. Keep previous versions and portable folders separate; a version rollback does not restore your settings.

For DEB packages, sudo apt remove automexia-terminal removes the application. For RPM packages, use sudo dnf remove automexia-terminal. Review the proposed changes first. For portable packages, close Automexia and remove only the folder you created for that version. Keep your configuration unless you intend to reset it. See the versioned removal guide.

Official archive and terms#

The v0.4.0 release contains the packages, signed evidence, release notes, and third-party notices. Review the terms bundled with the package. Product source remains private; future licensing and commercial plans are undecided.