Public roadmap#

Automexia is becoming a dependable workspace for command-line work. This roadmap communicates product direction without publishing private execution plans, security-sensitive details, or speculative delivery dates.

Now — make the terminal dependable#

The current priority is a stable terminal workspace people can trust for daily work. The project is improving:

session, tab, and pane reliability;
clear workspace and shell context;
configuration safety and predictable recovery;
keyboard, display, and accessibility behavior;
installation, testing, packaging, and release confidence.

Work is considered complete only when it is tested on its supported platforms and documented for users.

Next — make daily work easier#

After the core release is dependable, Automexia will make common terminal work faster to understand and easier to resume. The next themes are:

quicker navigation between related sessions;
clearer search and command history;
smoother shell and workspace setup;
safer shortcuts for repeated tasks;
better guidance when a command or connection fails.

These are direction statements, not promises for a specific release or date.

Later — support focused workflows#

Automexia may later add optional tools for specialized command-driven work. Those tools must remain separate from the terminal core, respect existing command-line tools, and keep important actions under user control.

Ideas move into public documentation only after their scope and safety are clear. Experimental architecture and implementation sequences stay in private planning until they are ready for public review.

How priorities are chosen#

The project favors work that:

improves reliability for current users;
reduces confusion without replacing the shell;
works across supported platforms;
remains understandable and reversible;
can be tested and maintained over time.

What this roadmap intentionally leaves out#

The public roadmap does not include exact launch dates, private dependencies, unreleased technical designs, unresolved security gaps, commercial strategy, or step-by-step implementation plans. Those details are kept outside the public website and public repository.

Use the feature catalog to preview the intended alpha experience. Read the product vision for the principles behind this direction.