Shell integration#

Shell integration supplies directory and command context while leaving editing and execution in the shell. Linux Public Alpha is available. This broader reference includes planned Windows behavior; check the Alpha limitations and your installed automexia --help before relying on a specific integration command.

What it adds#

When supported by the active shell, integration can provide:

the current working directory;
prompt and command boundaries;
command completion status and duration;
shell, user, and environment identity;
safer session cloning and clearer workspace context.

This information improves navigation and presentation. It does not give Automexia ownership of your commands.

Session-only by default#

The planned default loads integration only into the child shell Automexia starts. A normal launch will not rewrite a PowerShell, Bash, Zsh, or Fish profile.

If integration resources are missing or rejected by the operating system, the session falls back to the unmodified shell.

Supported shells#

Environment	Behavior
PowerShell	Loads supported prompt and directory metadata in the Automexia session.
Command Prompt	Uses a semantic prompt and UTF-8-aware session setup where available.
Bash and Zsh	Uses shell-native hooks without replacing the prompt body.
Fish	Uses Fish lifecycle hooks while preserving Fish editing and completion.
WSL	Treats the selected distribution as its own Linux environment.

The shell stays in control#

PSReadLine, Readline, ZLE, Fish, or the active terminal application continues to own:

text editing and cursor movement;
quoting and expansion;
command history;
native completion and suggestions;
aliases and functions;
the final command sent for execution.

Automexia does not calculate shell completions from pixels or rendered terminal cells.

Command results#

When the shell provides a trustworthy command boundary, Automexia can visually separate completed output from the next prompt. The treatment does not insert terminal rows, change copied text, or send input to the shell.

If the boundary cannot be proven, Automexia leaves the terminal output unchanged.

Directory and session context#

Directory metadata must be absolute and free of terminal control characters before it can update a session. Invalid metadata is ignored.

Context discovery runs away from the input and rendering path so a slow repository or external tool does not block typing.

File listings#

Optional listing presentation can add recognizable file and folder icons while preserving the real shell objects or native command fallback.

Set AUTOMEXIA_PLAIN_LS=1 before the integration loads when you want an unmodified listing.

Persistent installation#

Persistent integration is optional and should be used only when you want Automexia metadata in nested shells. Review profile changes before applying them and keep the operating system’s script policy in force.

When listed by the installed executable, start with the read-only diagnostic:

text

automexia shell-integration doctor

The commands below describe explicit persistent integration. Confirm their availability in your installed release, back up profiles first, and review the proposed changes. Do not run them merely to make the terminal start:

text

automexia shell-integration install
automexia shell-integration uninstall

Privacy and safety#

Integration does not require uploading terminal output.
Missing or malformed metadata fails back to normal shell behavior.
Profile installation is explicit.
Operating-system execution policy remains authoritative.
Secrets should stay in the credential tools that already own them.

See Start and launch, Configuration, and Troubleshooting.