MyUtils

An easy utility manager for you lazy efficient folk.

Your easy utiltiy manager for, .cmd, .bat, .ps1, and .exe files with more automation lists to come. We all hate that feeling of scrolling through folders looking for a script or running tree 3000 times on linux. Here, there's no worry, just plop your supported filetypes in the same folder directory and bam you're done.

Features

• Zero-config auto-discovery - recursively scans a folder tree for executables and scripts. No JSON/YAML config file to write or maintain.
• Type-aware menus - Executables (.exe), Batch Scripts (.bat), Command Scripts (.cmd), and PowerShell Scripts (.ps1) each get their own menu, but only appear if a file of that type actually exists somewhere in the tree.
• Keyboard-only navigation - arrow keys to move, Enter or Space to select, Esc or a pinned QUIT/BACK bar to exit. No mouse required.
• Single static binary - no installer, no .NET/VC++ Redistributable dependency, no DLLs to ship alongside it.
• Persistent default folder - set a default scan directory once, then just run myutils from anywhere.

Winget download

winget install Rphasical.MyUtils

Manual download

Grab the latest myutils.exe from the Releases page. It's a single portable executable - no installation required.

You must link the folder you dowload the .exe in to PATH

Search change environment variables in the searchbar, click it, and then click on path and add your folder containing myutils.exe

Note: This binary is not code-signed. Windows SmartScreen may show an "Unknown Publisher" warning the first time you run it - this is expected for an unsigned indie tool. Click More info → Run anyway to proceed. You can verify the download against the SHA-256 checksum published with each release.

Usage

myutils                       Scan the saved folder, or the current folder if none is saved
myutils -dir "C:\path"        Scan a specific folder for this run only
myutils "C:\path"             Same as above (bare path also accepted)
myutils -dir set "C:\path"    Save a default folder, then scan it
myutils -dir show             Print the currently saved folder
myutils -dir clear            Forget the saved folder
myutils -h, --help            Show usage

Typical setup

Set a default folder once:

myutils -dir set "C:\Scripts"

From then on, just run myutils from anywhere and it scans C:\Scripts automatically.

Folder resolution order

When run with no arguments, MyUtils picks a folder to scan in this order:

1. A folder passed on the command line (-dir or a bare path) - this run only, nothing is saved.
2. A previously saved default folder (set via -dir set).
3. The current working directory.
4. The folder the MyUtils.exe file itself lives in (useful when double-clicking a portable copy dropped next to your scripts).

Controls

Key	Action
↑ / ↓	Move selection
Home / End	Jump to first / last item
PgUp / PgDn	Jump a page at a time
Enter / Space	Select / launch
→	Same as Enter/Space
←	Back (same as Esc)
Esc	Back one level, or quit from the main menu

How it works

At startup, MyUtils resolves which folder to scan (see resolution order above), then walks that folder and all subfolders looking for files ending in .exe, .bat, .cmd, or .ps1. It creates a menu for each file type it finds, leaving out completely any empty categories and if nothing appears at all, the main menu simply displays "No utilities loaded".

If you select a file, it opens in the current console window, and when it ends, MyUtils redraws and you’re back at the menu.

The saved default folder (if you have set one with -dir set) is saved in a small per-user config file in %APPDATA%\MyUtils\config.json. This location is used specifically because it survives winget upgrade - the folder that winget actually installs the executable into is replaced on every upgrade so nothing should be saved there.

Building from source

Requirements: Visual Studio 2022 (or later) with the Desktop development with C++ workload, C++17 or later.

1. Clone the repo and open myutils.slnx (or the .sln) in Visual Studio.
2. Set the configuration to Release / x64.
3. Build → Rebuild Solution.
4. The compiled binary will be at x64\Release\myutils.exe. The project links the C++ runtime statically (/MT in Release), so the resulting .exe has no external runtime dependency and runs on a clean Windows machine without needing the Visual C++ Redistributable installed.

License

MIT - see LICENSE.

Author

Ray Bunton, 2026