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. It keeps related terminal sessions together without changing the tools inside them.
Organization should support the command line#
The product direction uses workspaces, tabs, and split panes to give each part of a task a stable place. A workspace can hold the sessions that belong to one project or operation. Tabs separate activities. Panes keep commands visible when they need to be compared.
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.
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?
Automexia plans to make useful session context visible near the work. That context may include the operating system, user, branch, environment, path, and command result when the information is available.
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.
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 session restoration. Bringing a workspace back should help someone resume a task, but restored state must remain understandable. A large set of unnamed sessions is not useful simply because it survived 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. Early Access feedback will help 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.
Automexia is not valuable because it puts more controls around a prompt. Its value is helping terminal work keep its shape as the task grows.