CLI Tools Cabinet changelog

1.6.1

November 5, 2026

The app’s search field now matches tool descriptions too, like clitools search already did. Searching “zones” finds a Cloudflare DNS tool even when “zones” isn’t in its name.
Counts of one read “1 tool” and “1 run”, instead of “1 tools”, in the app’s list header and in the clitools footers.

November 4, 2026

Automatic updates with your license key. The license key from your purchase now turns on automatic updates: enter it in CLI Tools Cabinet → License…, or when CLI Tools Cabinet → Check for Updates… asks for it. CLI Tools Cabinet works without a key, as before. A key works on 3 Macs, and License… → Deactivate This Mac frees one.

October 8, 2026

Renamed the app to CLI Tools Cabinet.

Existing saved data stays available. The companion command keeps its existing name. In-app update links now use the renamed repository.

October 7, 2026

~/bin is always scanned. Scripts and binaries you dropped in ~/bin show up as local tools, even when ~/bin isn’t on your PATH. The clitools command finds them too.
The app reads your shell’s PATH. Apps opened from Finder or the Dock get a short system PATH, so the app missed the folders your .zshrc, .bash_profile or config.fish adds, like ~/.composer/vendor/bin, and dropped those tools on its next scan. Now it asks your login shell for its PATH when it starts, and finds the same tools as clitools in your terminal.

October 5, 2026

A compact tool list. When the window is narrow and the tool details are open, the list used to squeeze the name, description, source and install date into a tiny column, and the names wrapped one letter per line. Now each row shows just the tool’s icon and name, and long names end with an ellipsis. Make the window wider and the full rows come back.
The section title stays on one line. Titles like “Installed Today” shrink a little instead of wrapping, and the tool count hides when there’s no room for it.

The clitools command didn’t change.

October 5, 2026

clitools capabilities. A tool can describe itself with a capabilities command: a summary, the tasks it can do with a command for each, and what changed in every version. clitools capabilities postdeck asks a tool and saves the answer in the catalog, and clitools capabilities --all --json lists what every tool that answered can do, in one call. clitools describes itself the same way.
Search by what a tool does. clitools search slideshow also matches the capabilities a tool lists, not only its name and description.
Only tools that support it get asked. clitools runs capabilities only on tools whose --help lists it, so a tool that would read the word as a file name or a prompt never sees it.
Your own commands in /opt/homebrew/bin. A script you link there from your home folder now shows up in the catalog. Before, only Homebrew packages did.

October 3, 2026

No more security warning. The first time you opened CLI Tools Cabinet, macOS used to say it “could not verify CLI Tools Cabinet is free of malware”, and you had to click Open Anyway in System Settings. Now it opens like other apps you download: macOS asks if you’re sure you want to open an app from the internet, and you click Open.
Nothing else changed.

September 30, 2026

One catalog. It finds the packages you explicitly installed with Homebrew, npm and Cargo, and scans trusted user command directories. A package’s commands stay grouped, so helper executables don’t flood the list.
Your history and your agents’ history. Select a tool to see the commands that ran it from your shell history (zsh, bash and fish). Click Find agent runs to see the ones Cursor, Codex and Claude Code ran.
Details when you ask. Inspecting a tool runs it with --version and --help, and fetches its description and examples. It only happens for the tool you select, never during a scan.
The clitools CLI reads the same catalog, with JSON output that AI agents can use. Install it from source with ./Scripts/install-cli.sh.
Updates from inside the app. Once a day, CLI Tools Cabinet asks GitHub whether there’s a newer version, and Install and Relaunch puts it in place. CLI Tools Cabinet → Check for Updates… checks right away.