Automexia User Guide#

Use this guide when you have a development build and want to learn one task at a time. Begin with your first session if you have not opened Automexia yet. Linux is the first development focus; Windows, macOS, and BSD examples elsewhere in this guide do not announce available packages or verified compatibility.

1. Start and arrange sessions#

First learn which shell and folder a session uses. Then decide whether work belongs in another window tab, a visible split, or a pane-local tab.

• Start a session in the right shell and directory
• Reuse a named terminal profile
• Understand windows, tabs, panes, and sessions
• Choose between a fresh and cloned split
• Find the keys and input controls you use often
• Restore a useful layout after restart

Restoring a layout opens fresh shells. It does not resume processes or reconnect remote hosts.

2. Read and return to your work#

Commands stay in the shell. Automexia helps you find retained output, inspect links and images, and understand a completed result.

• Run commands and review integrated results
• Search retained output
• Open links and preview local images
• Inspect wide table output
• Use browser search and bounded local tools
• Follow example layouts and workflows

For the interface behavior behind these tasks, read Terminal experience. For the complete feature map, use the feature catalog.

3. Customize and reuse#

Start with defaults. Change a visible preference in the interface when it offers that control; use Profiles for named launch recipes and the configuration file for the default shell and advanced settings. Saved actions remain review-first.

• Choose between in-app controls and config.toml
• Copy a small settings example
• Create, review, and manage Quick Actions
• Look up exact settings
• Look up exact keys and action names

4. Work with remote systems#

OpenSSH and provider tools remain responsible for connections, credentials, and remote commands. These pages distinguish three different SSH paths:

• Run ordinary SSH and use WSL as its own environment
• Use the optional, explicit +ssh wrapper
• Review SSH aliases in the read-only Connection Hub

The Hub does not start a managed connection. Check Platform support before treating any WSL or non-Linux behavior as verified.

5. Find help or an exact answer#

• Troubleshoot a development build
• Read short answers to common questions
• Check accessibility considerations
• Understand shell integration