Skip to content

Releases: flaviocopes/cli-tools-cabinet

CLI Tools Cabinet 1.5.0

Choose a tag to compare

@flaviocopes flaviocopes released this 08 Oct 08:25

Renamed the app to CLI Tools Cabinet. Updated the app name, GitHub repository and download names.

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

Install

Download CLI-Tools-Cabinet-1.5.0.zip, unzip it, and move CLI Tools Cabinet.app to your Applications folder. This universal build supports Apple silicon and Intel Macs, is signed with my Developer ID and notarized by Apple.

You can also build the source locally with the instructions in the README, using free Xcode tools.

SHA-256

1f4eeb89475cdf695648396220669b9defbecf2da7a59c0786af1536fedf6bbc  CLI-Tools-Cabinet-1.5.0.zip

CLI Tools Cabinet 1.4

Choose a tag to compare

@flaviocopes flaviocopes released this 07 Oct 07:42

CLI Tools Cabinet 1.4 finds the commands you put in ~/bin by hand, and the app now sees every folder your shell adds to your PATH.

What's new

  • ~/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.

Install

If you already use CLI Tools Cabinet, it offers this update by itself. Click Install and Relaunch, or choose CLI Tools Cabinet → Check for Updates… to get it right away.

Otherwise, download CLI-Tools-1.4.0.zip, unzip it, and drag CLI Tools Cabinet to your Applications folder. It runs on macOS 14 Sonoma or later, on Apple silicon and Intel Macs.

The catalog lives in ~/Library/Application Support/CliTools/catalog.json, and nothing from your shell history or agent transcripts is written to it.

SHA-256 of the zip: 6c6de24d6a931f167a2a1d3256a9c6ca1e0da6c3b70fee5b9149c72cb57b0f9a

CLI Tools Cabinet 1.3

Choose a tag to compare

@flaviocopes flaviocopes released this 05 Oct 13:23

CLI Tools Cabinet 1.3 keeps the tool list readable when the window is small.

What's new

  • 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.

Install

If you already use CLI Tools Cabinet, it offers this update by itself. Click Install and Relaunch, or choose CLI Tools Cabinet → Check for Updates… to get it right away.

Otherwise, download CLI-Tools-1.3.0.zip, unzip it, and drag CLI Tools Cabinet to your Applications folder. It runs on macOS 14 Sonoma or later, on Apple silicon and Intel Macs.

The catalog lives in ~/Library/Application Support/CliTools/catalog.json, and nothing from your shell history or agent transcripts is written to it.

SHA-256 of the zip: 27ded4ccf3ad5474444ca0baa8a1caacabbafdb76ca237335f960a59af5bc739

CLI Tools Cabinet 1.2

Choose a tag to compare

@flaviocopes flaviocopes released this 05 Oct 07:28

CLI Tools Cabinet 1.2 teaches the clitools command to ask your tools what they can do, so AI agents can pick the right one for a task.

What's new

  • 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.

Install

If you already use CLI Tools Cabinet, it offers this update by itself. Click Install and Relaunch, or choose CLI Tools Cabinet → Check for Updates… to get it right away.

Otherwise, download CLI-Tools-1.2.0.zip, unzip it, and drag CLI Tools Cabinet to your Applications folder. It runs on macOS 14 Sonoma or later, on Apple silicon and Intel Macs.

The catalog lives in ~/Library/Application Support/CliTools/catalog.json, and nothing from your shell history or agent transcripts is written to it.

SHA-256 of the zip: be2f619b22a1ae9aef53b4463cea3e20770beecce19de7ebd6a2ab286b2d7ba0

CLI Tools Cabinet 1.1

Choose a tag to compare

@flaviocopes flaviocopes released this 03 Oct 09:47

CLI Tools Cabinet 1.1 is signed with my Apple Developer ID and notarized by Apple.

What's new

  • 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.

Install

If you already use CLI Tools Cabinet, it offers this update by itself. Click Install and Relaunch, or choose CLI Tools Cabinet → Check for Updates… to get it right away.

Otherwise, download CLI-Tools-1.1.0.zip, unzip it, and drag CLI Tools Cabinet to your Applications folder. It runs on macOS 14 Sonoma or later, on Apple silicon and Intel Macs.

The catalog lives in ~/Library/Application Support/CliTools/catalog.json, and nothing from your shell history or agent transcripts is written to it.

SHA-256 of the zip: 68f3f494f56e7797a8707797ae7a842f6bbe05877261dccd293138c11580e93e

CLI Tools Cabinet 1.0

Choose a tag to compare

@flaviocopes flaviocopes released this 30 Sep 13:02

CLI Tools Cabinet gives you one catalog for every command-line tool on your Mac. This is the first release with a download, so you don't need to build the app yourself anymore.

What's in 1.0

  • 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.

Install

Download CLI-Tools-1.0.0.zip, unzip it, and drag CLI Tools Cabinet to your Applications folder. It runs on macOS 14 Sonoma or later, on Apple silicon and Intel Macs.

CLI Tools Cabinet isn't signed with an Apple Developer ID or notarized, so the first time you open it, macOS says it "could not verify CLI Tools Cabinet is free of malware". Click Done, then either:

  • open System Settings → Privacy & Security, scroll down to CLI Tools Cabinet, and click Open Anyway.

The README has the details, including what to do on a work laptop.

The catalog lives in ~/Library/Application Support/CliTools/catalog.json, and nothing from your shell history or agent transcripts is written to it.

SHA-256 of the zip: e25245c6a99ad1f43ea79717ae2010066d2296354f82f075b743231182bdbd37