All guides
Troubleshooting

Fix “um: command not found”

Check the installation, executable directory and shell before reinstalling anything.

Source-based guidance. No ModLab in-game reproduction has been completed for this guide.

Separate plugin and CLI installation

An agent finding skills does not prove that your terminal can find the um executable. Confirm which installation path you used.

Run the help command in a normal terminal and keep the exact output.

um --help
uv tool list
uv tool dir --bin

Inspect PATH

If uv lists universal-modder but um is missing, compare the executable directory reported by uv with your shell PATH. Follow uv’s own shell setup guidance and restart the terminal.

Check the terminal used by the agent too. A desktop app may have a different environment from your interactive shell. Do not add arbitrary directories or download replacement executables from unrelated sites.

Verify the fix

The expected first result is um displaying its command help. This validates CLI discovery only; it does not validate a game mod.

If it still fails, record OS, shell, installation command and complete error output for diagnosis. Remove any credentials before sharing logs.

Check the source

Compare version-sensitive instructions with the current upstream documentation.

Upstream documentation ↗

Keep exploring