Use Automexia `+ssh`#

The current public source implements an explicit +ssh command. It launches your system OpenSSH client and, when conditions permit, adds temporary shell integration to the remote interactive session. It is separate from the Connection Hub, whose managed Connect action is not active. This page documents source behavior; verify automexia +ssh --help in the build you use. The website does not offer a binary download.

The name is shared with Ghostty's +ssh, but the commands are not interchangeable. Ghostty focuses on preparing the remote terminal environment and terminfo; Automexia focuses on optional interactive shell integration and context. Use Automexia's options below, not Ghostty's flags.

Decide whether to use it#

Use ordinary ssh host-alias for the familiar OpenSSH experience or for a remote command, tunnel, file transfer, unusual shell, or configuration the wrapper cannot classify. Use +ssh when you want a deliberate interactive SSH session with Automexia prompt/context information and you know the account's shell. Both paths leave authentication, host-key checks, agents, proxy rules, and networking with OpenSSH.

text

automexia +ssh --shell bash -- staging

Here --shell bash describes the remote account shell, and -- separates Automexia options from native SSH arguments. The CLI also accepts automexia ssh as an alias for +ssh. The public source docs use amx +ssh through the installed Windows console launcher; do not assume a Linux amx helper is installed globally outside an integrated session.

Pick an integration mode#

Mode	Use it when	Behavior
`auto` (default)	You want enhancement only when the invocation is compatible.	Classifies the effective OpenSSH setup; otherwise takes a documented native path or stops before connecting if configuration cannot be safely classified.
`off`	You need plain OpenSSH behavior.	Passes through without injected remote metadata.
`required`	The enhanced local path is essential to this task.	Rejects unsupported local conditions rather than quietly starting a different experience; the remote shell still determines actual support.

For example, use automexia +ssh --integration off -- host-alias to keep wrapper invocation but explicitly use native SSH. Use --integration required --shell zsh -- host-alias when you would rather receive an error than lose the enhanced prompt. The wrapper preserves SSH's exit status. It does not infer a shell from a host name: choose bash, zsh, fish, powershell, or pwsh only when that matches the remote account. An unknown shell stays native.

Understand when it stays native#

An explicit remote command, SSH control operation, redirected streams, or incompatible effective configuration is not an ordinary enhanced interactive login. auto leaves those on the native path rather than inserting prompt metadata into command output. If effective configuration cannot be read/classified, auto stops before connecting; off is the explicit way to request native passthrough. The optional --force-tty requests a remote PTY with redirected streams, but cannot restore local resizing or interruption behavior that a process bridge lost.

Examples of tasks better left to system tools:

text

ssh staging 'uptime'
scp ./report.txt staging:~/reports/
ssh -L 8080:localhost:80 staging

Do not assume +ssh uploads a credential, modifies ~/.ssh/config, installs a remote profile, or reconnects a cloned pane. It does none of those by default. A remote context badge is display-only, not proof that a host is trusted.

Optional context discovery helper#

--helper-upload <path> explicitly stages a trusted helper matching the remote OS and architecture in a private temporary directory for the session. It can discover remote Git, Kubernetes, Docker, Terraform, and cloud context for display. This is not a provider login. It is not part of default +ssh startup, and only supported enhanced interactive shell targets qualify. The source currently supports POSIX Bash/Zsh and Windows PowerShell 5/7 for upload; Fish and Unix PowerShell can use ordinary integration without this helper.

The helper path is your choice and trust decision. Staging can involve two SSH invocations and two authentication prompts. It is time/size bounded, but interruption can leave temporary remote files; follow the source library guide for cleanup details before opting in. Do not upload an arbitrary executable just to make a badge appear.

Check a proposal without connecting#

automexia ssh-integration status reports the managed-SSH gate and wrapper availability. automexia ssh-integration inspect -- host-alias produces a redacted, non-executing plan. Neither command authenticates or authorizes a real session. The managed Connect path remains disabled; use OpenSSH itself for a connection. See Remote sessions and WSL for ordinary SSH, transfer, forwarding, and side-by-side workflows.

Use Automexia +ssh#