Skip to main content
AutomexiaDocsv0.4.0
Ctrl K

Workflow recipes#

These recipes show how small workspace choices keep projects clear. Use the Linux Alpha guide for current shortcuts and confirm advanced options with automexia --help. Windows and macOS examples describe planned support.

Recipe 1: Open a project and create a useful working layout#

Start in the project directory:

text
automexia --working-dir D:\work\my-project

or:

text
automexia --working-dir ~/work/my-project

Then:

  1. Keep the first pane for normal commands/editing launchers.
  2. Clone right with Ctrl+R so the second pane begins from the same launch profile/directory.
  3. Use the right pane for a server, watcher, REPL, or logs.
  4. Add a fresh lower split with Ctrl+Shift+D on Windows/Linux/BSD or Cmd+Shift+D on macOS when you want an independent default-shell task runner.
  5. Navigate panes with Alt+Arrow or Cmd+Alt+Arrow.

Why this works: cloning is ideal for “same project, another shell”; a fresh split is ideal for “another standard session.”

Recipe 2: Separate projects without creating desktop clutter#

Use window-level tabs:

  1. Open project A.
  2. Create another window-level tab with Ctrl+T / Cmd+T.
  3. Change to project B in that tab.
  4. Switch whole contexts with Ctrl+Tab / Ctrl+Shift+Tab.

Use separate OS windows instead when the projects belong on different monitors/desktops or you want independent minimize/close behavior.

Recipe 3: Keep one pane stable while rotating utility sessions#

Suppose the left pane is your main task shell and the right pane is your utility area.

  1. Split right.
  2. Focus the right pane.
  3. Create pane-local tabs with Ctrl+Shift+T / Cmd+Shift+T for a database console, log view, and secondary shell.
  4. Switch only those right-pane sessions using Alt+PageUp/PageDown or Cmd+Alt+[ / Cmd+Alt+].

The left pane remains visible and unchanged. This is exactly what pane-local tabs are for; using window tabs would swap too much of the workspace.

Recipe 4: Search old output without changing the command line#

Use terminal search rather than shell history:

  • Linux (and planned Windows/BSD): Ctrl+F for the selected pane, or Ctrl+Shift+F for all visible panes
  • macOS: Cmd+F

Type the text, press Enter for the next match and Shift+Enter for the previous. Esc cancels.

Use shell history (Up or Ctrl+Alt+R in the Linux Alpha defaults) to retrieve commands you typed. Ctrl+R clones a split in this release. Use Automexia search for text that appeared in terminal scrollback.

Recipe 5: Copy terminal text without losing normal Ctrl+C#

On Windows/Linux/BSD:

  1. Select text with the mouse or Shift+Arrow.
  2. Press Ctrl+C to copy it.
  3. Clear/exit selection by typing or using an unmodified Arrow.
  4. With no selection, Ctrl+C once again sends the normal interrupt to the shell/application.

If you prefer a dedicated copy chord, use Ctrl+Shift+C.

This design avoids forcing you to choose between terminal copy and shell interrupt globally.

Recipe 6: Preview an image filename from output#

If a command prints a local PNG/JPEG/WebP/etc. path:

Fast mouse approach: hover the filename, then click to pin.

Keyboard approach: select the path and press Ctrl+Alt+I or Cmd+Alt+I.

When pinned, use Arrow keys to move through other visible image paths and Esc to dismiss.

Use inline terminal graphics instead when an application itself is image-aware. Use an external app for PDF/SVG/editing/unsupported or remote resources.

Recipe 7: Launch a dedicated REPL/tool directly#

For a one-purpose terminal window, use -e:

text
automexia --working-dir ~/work/project -e python

This is appropriate for a REPL or interactive program that is itself the session. If the command depends on shell syntax such as |, >, aliases, or command substitution, open the normal shell and type it there instead.

Recipe 8: Make a temporary shell choice without changing config#

Need PowerShell just for this session?

text
automexia -e pwsh -NoLogo

Need Zsh for one launch?

text
automexia -e zsh -l

If you keep doing this every day, move the choice into [shell] in config.toml. Temporary launch options should remain temporary; permanent preferences belong in config.

Recipe 9: Diagnose shell integration before modifying profiles#

If prompt context or integrated listings look wrong:

text
automexia shell-integration doctor

Then check:

  • whether the session is really running inside Automexia;
  • whether TERM_PROGRAM=Automexia / the integration marker is present where expected;
  • whether the installed integration resources are available;
  • the relevant item in Troubleshooting.

Do not force-install profile hooks as a general repair. Back up profiles and follow the release's shell integration guidance before considering a persistent change; normal launch is designed to be session-only.

Recipe 10: Customize safely in small steps#

  1. Create a starter:

    text
    automexia --write-config

  2. Open it with Ctrl+,, Ctrl+Shift+,, or Cmd+, depending on platform.

  3. Change one thing—such as font size or shell.

  4. Restart or use a configured reload action.

  5. Verify the result.

  6. Add another change only if it solves a real need.

If a config reload fails, Automexia keeps the last known-good runtime configuration, so fix the parse/theme error rather than layering more changes on top.

Recipe 11: Local + SSH side by side#

  1. Start a local project shell.

  2. Create a fresh split for a clean remote launcher.

  3. In the second pane run:

    text
    ssh host-alias

  4. Keep the first pane local for code/files/builds.

  5. Use geometric pane navigation to move between local and remote.

OpenSSH remains the authority for keys, agents, host-key policy, proxy jumps, and configuration.

Recipe 12: Use WSL without putting Linux build work on /mnt/c#

On Windows, keep Linux-heavy repositories in a WSL-native location such as:

text
~/src/my-project

Use NTFS for native Windows/MSVC work. Treat Windows and WSL as separate tool/config/cache/trust environments rather than trying to share Cargo target directories or persistent generated shell artifacts across the boundary.

This avoids the filesystem I/O penalty and reduces cross-environment state confusion.

Recipe 13: Organize a media-processing workflow#

Automexia does not include built-in video editing today, but it can organize command-line media tools without pretending to replace them:

  1. Start in the folder that contains the source media and project files.
  2. Keep one pane for listing sources, checking metadata, and choosing inputs.
  3. Clone a second pane for FFmpeg or a project-owned processing script.
  4. Add a lower split for progress, logs, or validation output.
  5. Preview generated still images through the supported image workflow.
  6. Use a separate window-level tab for a different job or output set.

The selected media tool performs the transformation; Automexia keeps the commands, files, output, and progress easier to follow.

When a recipe stops fitting#

Recipes are meant to explain the intended composition of features, not become another hidden specification. When you need an exact option/key/setting, jump to:

When behavior is failing rather than merely unfamiliar, use Troubleshooting.