Frequently asked questions#
Short answers about Automexia's development preview and public source.
Understand Automexia#
What is Automexia?#
Automexia is a customizable terminal with a focused core and useful defaults. Keyboard controls help you move between tasks, while visible context and readable output help you review results. Your shell still runs the commands.
For a concrete layout, see the workspace hierarchy.
Does it replace PowerShell, Bash, Zsh, Fish, or WSL?#
No. Your shell owns commands, scripting, completion, startup files, and history. Automexia provides the surrounding terminal workspace. Its named profiles choose how a new session starts; they do not replace your shell's own configuration.
What can I explore today?#
Read the public source and explore the Linux development workflows. See Features for concrete examples and Development status for the current limits.
Availability and platforms#
Are installers available on this website?#
No. Package downloads have been withdrawn while the terminal is improved. Installation links to the official development setup instead.
Is Automexia ready for everyday use?#
It is still in development, not presented as stable or production-ready. Evaluate non-sensitive workflows and keep a trusted terminal available.
Is the source public?#
Yes. The official repository is AmjedAllaya/automexia. Its MIT license sets the source terms. That does not promise future pricing or service offerings.
Which operating systems are supported?#
Linux is the first development focus. Windows and macOS require further native validation. There are no website packages; see Platform support for the distinction between design and verified compatibility.
Everyday use#
Can I start without a configuration file?#
Yes. Start with defaults. For a visible change, use the in-app control if it
exists; use config.toml for lasting or advanced settings. The
customization guide
shows which path owns each setting.
How much can I customize?#
Choose themes, fonts, shortcuts, shell profiles, and supported presentation features. You can show or hide information tags, adjust output and Kubernetes status colors, and change table styling. Use the interface or a settings file. Some layout and input rules stay fixed; the customization guide explains each control.
Are specialized tools part of the core?#
The core handles ordinary terminal work. The extension design keeps optional tools separate so users can choose what they need. Public extension installation and activation are not available yet. Read the product principles for this boundary.
Where is configuration stored?#
The location follows the operating system. See the configuration reference for paths and reload behavior.
What is the difference between a tab and a pane?#
A window tab switches the whole workspace. A split keeps multiple panes visible; each pane hosts a terminal session and can have local tabs that change only that pane. See Workspaces, tabs, and panes for examples.
How do I discover shortcuts?#
Use the command palette and keyboard reference. Check the binding in the development revision you run.
Can I use SSH, Docker, Kubernetes, and cloud CLIs?#
Run their official tools in your shell. Those tools retain responsibility for
authentication, configuration, and network behavior.
For remote access, compare ordinary SSH, +ssh, and Connection Hub.
Does Automexia support images?#
The documented design covers selected terminal image protocols and explicit local image previews. See Files and images for supported formats and limits.
Does normal terminal use require an AI service?#
No. There is no AI agent directing normal terminal work. Your shell runs the commands, and the workspace works without a model, provider login, or paid API. You can use your own command-line tools and decide which services they access.
Safety and help#
How should I handle secrets?#
Use the operating system, SSH agent, or provider tooling that owns your credentials. Never put secrets in shared configuration, screenshots, or reports.
What happens if configuration is invalid?#
The documented reload behavior keeps the last valid configuration and reports the error. Check Troubleshooting if your revision behaves differently.
Where should I report a problem?#
Follow the repository's support guidance. Include a minimal, redacted reproduction and source revision. For a possible vulnerability, use the security policy, not a public issue.
Where should I go next?#
Read Getting started, then explore the User Guide and public roadmap.