A terminal can be fast and still become difficult to follow. One task turns into several tabs. A local server runs beside a test process. A remote session shares the screen with logs. Hours later, the commands still work, but the reason each session exists is harder to see.
Automexia is being built around that problem. A focused terminal core keeps your shell in control, while useful defaults and a clear interface help you follow the work. You choose how much of that interface you want to see.
A useful first session#
You should not need to assemble a collection of plugins before opening related sessions, searching output, or moving between panes. Automexia includes those everyday tools in its starting experience. You can begin without a settings file, then change the parts that matter to you.
Themes, fonts, shortcuts, information tags, output colors, and table styles have documented controls. Supported visual features can be enabled or disabled. The customization guide explains what the interface can change and when a file setting is needed.
Organization should support the command line#
Window tabs separate larger activities. Split panes keep related sessions visible together. Pane-local tabs let one area switch tasks while the others stay put. A server, its logs, and a second shell can each have a place without becoming one long, hard-to-follow session.
This structure is useful only when it stays out of the way. The active terminal must remain clear. Keyboard movement must be predictable. Opening a new session should not require navigating a dense control panel.
Automexia therefore treats the terminal as the main surface. Organization exists around it, not over it.
Shortcuts keep repeated actions close. The command palette gives unfamiliar actions a searchable name, so working from the keyboard does not require memorizing every shortcut first.
Context should answer useful questions#
People repeatedly check the same details during command-line work. Which directory is active? Which Git branch is checked out? Is this local or production? Did the previous command succeed?
When a shell or tool provides it, Automexia can show useful directory, branch, and command context near the session. Search can return you to retained output in the current pane or across visible panes.
It is not a second source of truth. Shell output and the tools themselves remain authoritative. The interface should reduce repeated checking, not hide what the command line says.
Results should be easier to read#
A table is useful when you can follow a row and compare its columns. Automexia can align supported tables and open a focused viewer for wide results. Output highlighting can draw attention to recognizable errors and observed Kubernetes states. The original text stays intact when you copy it.
For example, keep a service log beside a kubectl result. Clear rows and status
colors help you decide which output deserves a closer look. Use those cues to
guide your review, then confirm the result with the tool. The
table guide shows the workflow.
Keep specialized tools a choice#
Normal terminal work does not need an AI agent, model account, or paid API. Your shell runs the commands. Automexia supplies the workspace around it.
The extension design keeps optional tools separate from the terminal core. That lets the core remain useful on its own and makes additional complexity a deliberate choice. Public extension installation is not available yet; this principle does not announce an extension catalog.
Search should help you return to the work#
Long output is valuable only if it can be found again. Search, scrollback, selection, and clipboard behavior are part of the everyday experience rather than secondary extras.
The same principle applies to returning to a workspace. A recognizable layout helps you find a task again; it does not promise that a running process or SSH connection will survive a restart.
Familiar tools remain familiar#
Automexia is designed to work with established shells and command-line programs. Shell integration can improve awareness of directories, prompts, and command boundaries. It should not silently rewrite commands or pretend that every shell behaves the same way.
Platform and shell differences will remain documented. Development feedback helps separate intentional behavior from compatibility problems.
See the product direction#
The feature catalog distinguishes the planned experience from current availability. The workspace guide previews how sessions, tabs, and panes fit together. The terminal experience guide describes the interaction goals in more detail.
The goal is simple: keep the task understandable as it grows, while the command line remains yours.