Skip to main content
AutomexiaDocsv0.4.0
Ctrl K

Remote sessions and WSL#

Automexia hosts the command-line tools you already use. OpenSSH owns remote connections and credentials. Linux Public Alpha is available; Windows-hosted WSL sessions describe planned support, not a downloadable Windows release.

Connect with OpenSSH#

Run OpenSSH from the shell:

text
ssh host-alias

You can also provide an explicit user and host:

text
ssh user@example.com

OpenSSH remains responsible for keys, agents, certificates, host verification, proxy jumps, ports, and configuration precedence. Automexia hosts the session; it does not replace the SSH security model.

Keep repeated hosts in OpenSSH config#

For a host you use often, define the alias in your normal OpenSSH configuration and connect with ssh alias. This keeps connection policy in the tool that understands it instead of hiding sensitive details in a terminal shortcut.

Work locally and remotely side by side#

  1. Keep a local shell in one pane.
  2. Open a fresh split.
  3. Run ssh host-alias in the second pane.
  4. Move between panes with the configured pane shortcuts.

A cloned pane copies the local launch context. It does not duplicate an already running remote process.

Use port forwarding intentionally#

When you need a local forward, use OpenSSH syntax and review the listening address, destination, and host:

text
ssh -L 8080:localhost:80 host-alias

Follow your organization’s access and network policies. Automexia does not create tunnels in the background.

Use WSL as its own environment#

There is no Windows package yet. Running the Linux package under WSLg is not a verified compatibility claim. The guidance below concerns a future Windows application; see Platform support.

WSL has its own shell, filesystem, tools, profiles, packages, and trust state.

  • Keep Linux build-heavy repositories in the WSL filesystem when performance matters.
  • Keep native Windows toolchains and Windows-only work on NTFS.
  • Configure aliases and profiles separately inside each environment.
  • Use Automexia splits when you need Windows and WSL tools in the same workspace.

Remote safety#

  • Review host-key prompts before accepting them.
  • Keep credentials in established agents, keychains, and provider tools.
  • Avoid placing secrets in command text, aliases, logs, or copied examples.
  • Do not automatically retry destructive commands after a dropped connection.
  • Treat remote output and copied commands as untrusted input.

See Platform support and Workflow recipes for practical layouts.