Skip to main content

Product direction

Why Automexia starts with Linux

Linux gives Automexia a focused development starting point while the terminal's workflows and platform compatibility are improved.

Automexia is being built for people who spend real time in a terminal. Linux remains the first development focus. A smaller scope makes it easier to investigate problems, compare behavior, and explain the environment being evaluated.

This is not a claim that other systems matter less. Windows and macOS need their own native testing rather than assumptions based on Linux behavior.

Focus on the work before expanding the promise#

A terminal has to handle ordinary tasks consistently: selecting text, pasting a command, resizing a pane, finding output, and keeping focus where the user expects it.

These details matter more than a long list of platforms. A workflow that looks good in one screenshot can behave differently with another shell, display scale, or graphics environment.

The platform guide separates development direction from verified compatibility. Public source access does not make every platform ready.

Your shell stays in control#

Automexia gives related shell sessions a place to live without replacing Bash, Zsh, Fish, or the command-line tools people already know. Window tabs separate larger tasks. A split keeps a server and its logs in view; pane-local tabs let one side change without moving the other. The shell still interprets commands, and provider tools still own authentication and network behavior.

That boundary also makes reports more useful. A reproduction can distinguish a terminal focus problem from a shell configuration problem instead of treating both as an unexplained failure.

Follow development in the open#

The official repository is public. Readers can inspect changes and follow its development instructions. Its published license explains the source terms.

Website package downloads are withdrawn while issues are addressed. This is not a stable release announcement. If you evaluate a source build, begin with non-sensitive work and record the revision.

Getting started describes a cautious first session. Development status explains what to expect and how to prepare useful feedback.

Let evidence guide the next platform#

A broader platform offering should follow clear native requirements and useful testing, not a calendar promise.

The public roadmap keeps that direction visible without promising release dates. Starting with Linux gives Automexia a focused place to improve the experience before asking more people to rely on it.

Continue reading

More from Automexia