# How to Uninstall the Omarchy CLI: Complete Removal Guide

> Completely uninstall Omarchy CLI by deleting bin directories removing the root folder clearing user config and cleaning your PATH variable. Follow our guide for full removal.

- Repository: [Omacom/omarchy](https://github.com/omacom/omarchy)
- Tags: how-to-guide
- Published: 2026-09-12

---

**To completely uninstall the Omarchy CLI, delete the `$OMARCHY_PATH/bin` directory containing all `omarchy-*` scripts, remove the `$OMARCHY_PATH` root folder, clear the user configuration at `~/.config/omarchy`, and clean up your shell's `PATH` variable.**

The Omarchy CLI is distributed as a collection of standalone shell scripts rather than a system-managed package, which means no standard package manager handles its removal. Because the installation simply places executable files under `$OMARCHY_PATH/bin` and configuration in `~/.config/omarchy`, uninstalling requires manual deletion of these directories. Follow the steps below to ensure complete removal without leaving residual binaries or environment variables.

## Locate Your Omarchy Installation Root

Before removing files, identify where Omarchy resides on your filesystem. The CLI sets the environment variable `OMARCHY_PATH` at runtime to indicate its installation root.

Run this command to display the current value:

```bash
echo "$OMARCHY_PATH"

```

Common values include `/usr/local/omarchy` for system-wide installations or `$HOME/.local/omarchy` for per-user setups. Note this path for the subsequent deletion steps.

## Remove Omarchy Binaries and Core Files

All Omarchy CLI commands are shell scripts prefixed with `omarchy-` and stored in the `bin` subdirectory. Deleting this directory removes every executable command.

Execute the following to remove all binaries:

```bash
rm -rf "$OMARCHY_PATH/bin"

```

Next, delete the entire Omarchy tree to remove shared resources such as icons, desktop files, and auxiliary helper scripts:

```bash
rm -rf "$OMARCHY_PATH"

```

## Clean Up User Configuration

Personal settings and custom themes reside in the standard XDG configuration directory. If you want to erase all Omarchy customizations, delete the configuration folder:

```bash
rm -rf "$HOME/.config/omarchy"

```

This directory contains theme definitions, menu configurations, and user-specific tweaks that persist independently of the core installation.

## Handle Third-Party Dependencies

Certain Omarchy installation commands (such as `omarchy-install-dev-env`) may have installed external utilities like `mise`, `rustup`, `flatpak`, or language runtimes. These tools are **not** automatically removed when you delete the Omarchy CLI.

You must uninstall third-party tools manually using your system package manager. For example:

```bash

# Remove Rust installed via rustup

rustup self uninstall -y

# Remove packages on Arch Linux

sudo pacman -Rns package-name

# Remove packages on Debian/Ubuntu

sudo apt remove package-name

```

Review which auxiliary tools you installed through Omarchy helpers and remove them individually to avoid orphaned packages.

## Update Your Shell Environment

If you added `$OMARCHY_PATH/bin` to your `PATH` during installation, remove that line from your shell startup file. Edit `~/.bashrc`, `~/.zshrc`, or the appropriate rc file for your shell, and delete the export statement referencing Omarchy.

Use this `sed` command to automate the cleanup:

```bash
sed -i '/export PATH=.*omarchy/d' ~/.bashrc

```

Reload your shell configuration to apply the changes:

```bash
source ~/.bashrc

```

## Verify Complete Removal

Confirm that no `omarchy` commands remain accessible in your shell:

```bash
command -v omarchy

```

This command should produce no output if removal was successful. If it returns a path, repeat the binary deletion step for the specific location shown, then check again.

## Summary

- The Omarchy CLI installs as standalone scripts under `$OMARCHY_PATH/bin` with configuration in `~/.config/omarchy`.
- Delete the `bin` directory to remove all `omarchy-*` commands, then remove the entire `$OMARCHY_PATH` tree for shared resources.
- Clear user-specific settings by deleting `$HOME/.config/omarchy`.
- Third-party tools installed via Omarchy helpers (like `rustup` or `mise`) require manual uninstallation through your system package manager.
- Remove the `PATH` export from your shell rc file and reload your configuration to complete the uninstallation.

## Frequently Asked Questions

### How do I know where Omarchy is installed on my system?

Run `echo "$OMARCHY_PATH"` in your terminal. The Omarchy CLI sets this environment variable at runtime to point to either `/usr/local/omarchy` for system-wide installs or `$HOME/.local/omarchy` for user-specific installations. This path contains all executable scripts and shared resources.

### Will uninstalling Omarchy remove the programming languages it installed?

No, uninstalling the Omarchy CLI only deletes the shell scripts and configuration files. External tools such as `rustup`, `mise`, or language runtimes installed via `omarchy-install-*` commands persist on your system. You must remove these separately using their native uninstallers or your system package manager.

### Why does the `omarchy` command still work after I deleted the files?

If `command -v omarchy` still returns a path, your shell is caching the executable location or residual files remain. Run `hash -r` to clear the command hash table, or manually delete the specific path returned by `command -v`. Also verify you removed the correct `$OMARCHY_PATH` directory shown by the environment variable.

### Is there an automated uninstaller script for Omarchy?

No, the Omarchy repository does not provide an automated uninstaller because the installation is simply a directory of shell scripts. Complete removal requires the manual steps outlined above: deleting `$OMARCHY_PATH`, clearing `~/.config/omarchy`, and cleaning your shell's `PATH` variable.