Fix um Command Not Found in Universal Modder

An um command not found error means your selected shell cannot resolve the intended command. Check the command's location and installation in that environment. An agent skill that loads correctly does not put um on your ordinary terminal PATH.

Checks

In the terminal where the command failed, try um --help. On PowerShell, inspect all matching commands:

powershell

Select code

Get-Command um -All

You can select the code to copy it manually.

On Bash or Zsh:

Select code

command -v um

You can select the code to copy it manually.

For an installation made with uv, inspect the same environment's tool list and executable directory:

text

Select code

uv tool list
uv tool dir --bin

You can select the code to copy it manually.

If no intended CLI is installed, follow the standalone CLI setup. If it is listed but missing from the shell, follow uv tool update-shell instructions and open a fresh terminal. Keep existing PATH entries.

For an installation made with pipx, use its own inventory and paths:

Select code

pipx list
pipx environment

You can select the code to copy it manually.

Look for universal-modder, its exposed um command and the reported PIPX_BIN_DIR. If the package is installed but that executable directory is missing from PATH, run:

Select code

pipx ensurepath

You can select the code to copy it manually.

This can update your shell configuration. Open a new terminal, repeat command discovery and run um --help. Use the same user and installation scope as the original pipx install; do not create a second installation just to fix PATH. For more options, see the pipx installation guide and command reference.

Identify the environment

Claude's plugin hook prepares later agent Bash calls. It does not change every ordinary terminal. Gemini extension discovery likewise does not install a global CLI. Check the agent tool environment and ordinary terminal separately.

If um works but the agent cannot find mod-any-game, continue with Universal Modder plugin discovery rather than changing the executable path again.

Windows and WSL also have distinct paths and installed tools. Install or configure the CLI where you will use it rather than copying a host path into a Linux shell. If Get-Command shows an alias, function or another tool named um, inspect its origin before changing anything.

Command starts but fails

A Python or module error after um is found is a runtime dependency failure. Review the isolated tool environment, including Pillow, numpy and PyYAML, and preserve the exact error. Use the CLI error checks to classify that next failure. Reinstalling a skill does not necessarily repair that environment.

Verify

In the intended environment, check:

text

Select code

um --help
um --version

You can select the code to copy it manually.

Help should list the real subcommands, and the version check should report the installed release, such as universal-modder 0.2.0. The um CLI reference lists the command groups and argument syntax. Do not use scan, fal or game edits to test PATH. A command with exit code zero but unrelated output is not a pass. A newer agent plugin may bundle a different version; compare its package metadata and current instructions with the CLI you installed.

Continue

Return to Claude check CLI or Gemini check CLI. Check a fresh agent session as well as the ordinary terminal before starting your first Mod plan.

Preserve your setup

For an older installation, record its source and version before changing it; current installation instructions do not identify what is already on your machine. Keep unrelated tools, agent settings, project files and backups. Remove credentials and personal paths from any error you choose to share elsewhere.