Product vision#
Automexia puts a focused terminal core at the center of your work. Useful defaults make the first session approachable. Keyboard controls, readable output, and deep customization help you make the workspace your own.
The problem#
Complex work often spreads across several terminals, directories, machines, and tools. The commands still work, but the context around them becomes hard to follow. A warning gets lost in a long result. Similar sessions make it harder to tell where the next command will run. A useful interface should make those details easier to see.
The value#
Automexia should help people:
- start with useful terminal features already in place;
- move between related tasks without losing their context;
- spot command results and observed status changes more easily;
- compare rows in supported tables without changing the source text;
- choose useful controls and appearance settings for their own workflow.
Who it is for#
Automexia is for anyone whose work depends on a command line and grows beyond a single terminal. That includes developers, operators, administrators, researchers, and technical creators.
Product principles#
Keep the core focused#
The core handles everyday terminal work without an AI agent directing your session. Your shell owns commands; the tools you run own their credentials and connections. Normal terminal use needs no model, hosted account, or paid API.
Optional extensions are designed to stay separate from that core, with explicit boundaries for what they can access. The principle is simple: choose specialized tools when they help your work. Public extension installation and activation are not available yet.
Start useful, then make it yours#
Everyday features such as tabs, panes, search, and keyboard navigation belong in the starting experience. A configuration file is optional. You can then choose themes, fonts, shortcuts, and supported visual features through the interface or settings file. Keep useful details visible and turn off what you do not need. Some layout and input rules stay fixed to keep behavior predictable.
Put frequent actions within reach#
The interface should stay minimal while making useful actions easy to find. Shortcuts cover everyday work; the command palette helps you discover an action when you do not remember its key. A person should be able to work from the keyboard without needing to memorize every command in advance.
Make multitasking easier to follow#
Window tabs separate larger tasks. Split panes show related sessions together; pane-local tabs let one area change while its neighbors stay visible. Clear focus and available shell context help you review the active session before typing, pasting, or repeating a command.
Help people read before they act#
Command grouping and output highlighting help separate results and draw attention to recognizable errors or Kubernetes states. Supported tables gain aligned columns and readable rows. These cues aim to make review easier and reduce avoidable confusion. They do not prove a cluster is healthy or make a command safe: the original output and the producing tool remain the authority.
See command output, table output, and customization for examples and controls.
Today and tomorrow#
Today, the Linux development work focuses on reliable sessions, readable context, keyboard navigation, and clear documentation of what each source revision can do. Optional workflow tools remain separate from the terminal core and must not turn a suggestion into an unattended action.
The feature catalog describes current availability. The public roadmap communicates direction without exposing private execution plans.
The official repository publishes the source under its MIT license. Development status records the current readiness boundary without promising future commercial terms.