The Omarchy CLI: Controlling and Customizing Omarchy From the Terminal

Omarchy's menus and hotkeys are not the only way to control the system.

Running:

omarchy

opens the Omarchy command center in the terminal.

The important skill is not memorizing every command. It is learning how to ask the CLI what is available.

Start with command discovery

Current Omarchy CLI syntax includes:

omarchy commands --all

The command system also supports structured discovery options such as JSON/check output and help at both group and command level.

Examples:

omarchy capture --help

omarchy capture screenshot --help

That makes the CLI more durable than a copied command cheat sheet because you can inspect the version actually installed on your machine.

Representative commands

Current common commands include:

omarchy update

omarchy theme list

omarchy theme set <name>

omarchy font list

omarchy screenshot

omarchy debug

Those examples cover several different parts of the system: updates, appearance, capture and diagnostics.

The full CLI contains many more groups.

Groups organize the command surface

Current groups include areas such as:

• audio;
• battery;
• Bluetooth;
• brightness;
• capture;
• channel management;
• clipboard;
• configuration;
• debugging.

Instead of guessing a full command name, start with the group and ask for help.

That is especially useful after upgrades because command names and capabilities can evolve.

The CLI and menu are two views of the same system

Many Omarchy menu actions ultimately use the same tooling exposed through the CLI.

That means terminal users do not need to abandon supported Omarchy workflows just to avoid clicking through menus.

Examples include:

• changing themes;
• setting defaults;
• updating;
• opening menus at specific locations;
• gathering debug information.

The current CLI can even summon points inside the graphical Omarchy menu.

Why the CLI is useful with automation and AI agents

A terminal command is easier to describe, inspect and reproduce than a sequence of GUI clicks.

Omarchy's own manual specifically notes the CLI's usefulness when working with AI agents on configuration.

That does not mean an agent should be allowed to execute arbitrary commands blindly.

A safer pattern is:

1. discover the supported command;
2. inspect --help;
3. confirm what it changes;
4. run the narrow action;
5. verify the result.

The self-describing CLI helps keep those operations bounded.

Package commands still deserve caution

Omarchy exposes package-management helpers and menu paths for Arch/AUR software.

AUR packages are community-maintained and are not vetted in the same way as official Arch repository packages.

Do not translate "the CLI can install it" into "the package is automatically trustworthy."

Prefer supported commands over editing internals

If Omarchy already has a command for changing a default, applying a theme or performing an update, use that supported path.

Editing internal package files to imitate what a command does is more brittle.

For example, the default browser is handled through the supported default-setting command rather than manual XDG edits.

See How to Change the Default Browser in Omarchy.

For file-level customization boundaries, see How to Customize Omarchy Without Breaking Future Updates.

The CLI is best understood as a discoverable control surface, not a giant list you are supposed to memorize.