Omarchy Help

Operating boundaries

• Do not turn a focused config change or routine restart into a general health audit.
• Treat ~/.local/share/omarchy/ as read-only reference and upstream-managed state. Official Omarchy update or reinstall commands may manage it; never patch it manually for workstation customization.
• Read existing user config before editing. Preserve local structure, includes, overrides, and unrelated changes.
• Discover device names, services, installed applications, theme names, and command availability from the machine. Do not assume them.
• Routine user-config edits and scoped component reloads are authorized when they are part of the requested fix or change.
• Confirm unrequested destructive or materially disruptive actions: config refresh/reset, reinstall, package removal, snapshot restore, channel or branch changes, boot/security/storage changes, logout, reboot, and shutdown. Do not ask again when the user explicitly requested that exact action and its scope is clear.
• Do not use system updates, broad resets, or reinstall commands as speculative troubleshooting.

Reference

Read the relevant part of references/workstation-guide.md before changing Omarchy-managed config, themes, packages, updates, or recovery state. It documents ownership layers, current command discovery, component validation, and the difference between restart, refresh, reinstall, and update.

Workflow