Automexia is being built for people who spend real time in a terminal. The first Public Alpha, v0.4.0, is available for Linux x64 and Arm64. That smaller starting point gives the project a clearer way to publish, test, and explain its first packages.
This is a scope decision, not a claim that other systems matter less. Windows and macOS remain part of the broader direction. They will follow only when their native release paths are ready to carry the same level of installation and verification information.
A smaller promise is easier to trust#
Early Access should tell people exactly what they are evaluating. On Linux, Automexia provides DEB, RPM, and portable archive options. Native package checks cover Ubuntu 22.04 on x64 and Arm64; an RPM file does not imply Fedora certification.
The package page states what is available. The release notes state what was tested. Known limits stay visible. If a system is not included in that evidence, the website does not imply support.
That boundary matters more than a long platform list. It gives testers a precise answer to a basic question: is this package intended for my machine?
The shell stays in control#
Automexia is not trying to replace Bash, Zsh, Fish, or the command-line tools people already trust. It is designed to organize related sessions around those tools.
The product direction centers on workspaces, tabs, panes, searchable output, and useful session context. Your shell still interprets commands. Your existing tools still do the work. Automexia gives that work a clearer place to live.
This approach also keeps feedback useful during Early Access. A tester can separate a packaging problem, a terminal behavior problem, and a shell-specific problem instead of treating them as one unknown failure.
What changed when the first packages appeared#
The website now offers v0.4.0 Public Alpha after verifying the immutable release, its signed checksums, and all six packages. Alpha means this is an evaluation release, not a stable terminal for critical work.
The installation page provides the package choices, requirements, limits, and verification steps for that exact version. Unknown or inactive download routes remain unavailable instead of leading to a placeholder or an unverified file.
The Automexia source repository remains private. Early Access distributes application packages, not a supported source-build workflow. The final licensing and business model have not been announced.
Follow the public release boundary#
The Early Access guide explains what testers can expect. Installation remains the source of truth for package availability. Release trust explains how to identify and verify an official file.
Starting with Linux lets Automexia make one public promise and support it carefully. More platforms can follow when their release evidence is equally clear.