Aliases and packs

loadout ships 136 aliases. Most are on for everyone; the ecosystem-specific ones are grouped into packs and off until you ask.

The complete list is in the alias catalog, generated from the shipped source.

Turning one off

aliases:
  disabled: [py, dk]

Disabled entries are not generated at all. This is the right move for a name you already use for something else, or a shortening you find harder to read than the command it replaces. Nothing in the catalog shadows a familiar command — what loadout leaves out explains the bar an entry has to clear — but your habits are yours, and the catalog does not get a vote on them.

Adding your own

aliases:
  custom:
    - name: deploy
      command: ./scripts/deploy.sh
    - name: pbcopy
      command: xclip -selection clipboard
      platform: [linux]

platform limits an alias to linux, darwin, or both. Leave it out and it is generated everywhere.

Custom aliases are rendered exactly like shipped ones and go through the same quoting. A name colliding with a shipped alias overrides it, so you do not need to disable an entry just to replace it.

Note

Custom aliases have no requires declaration, so loadout doctor cannot tell you when the tool one points at is missing. That check exists for the shipped catalog because each entry there declares what it needs.

Packs

Packs are bundles for one tool or ecosystem, off unless listed:

packs: [flutter, cloudflared]

Pack	What it covers
ansible	Playbook and vault shorthands
cloudflared	Tunnel management
exercism	Exercise download and submit
flutter	Build, run, device and package commands
gatsby	Develop, build, new
git-flow	Feature and release branch commands
jekyll	Serve, build, and the bundler wrappers around them

Counts and the exact tools each needs are in the packs reference.

Enabling a pack whose tool is not installed is not an error. The aliases are generated, doctor reports the missing binary, and the web interface shows them amber — you may be setting up a machine before you have finished installing things.

Aliases your configuration generates

Some aliases do not come from the catalog at all; your configuration produces them.

• Hosts with shortcut: true get a bare ssh <alias> alias.
• Workspaces get an alias named after the workspace that opens it, and pairs with its tmux session if one is declared.
• Clone sources get a command that clones from the organisation you named.

This is why two people running the same version of loadout have different alias counts, and why loadout catalog shows more than 136 on a populated configuration.

Seeing what you have

loadout catalog             # everything, grouped by category
loadout catalog --enabled   # only what your config generates
loadout describe gpush      # one entry, in detail

The web interface is better for browsing, because it shows live availability — each alias with whether the tool it needs is actually installed here. A flat file cannot tell you which of your aliases point at tools you never installed.

After any change

loadout apply

Editing the configuration changes nothing on its own. The generated file is written only by apply.