CLI Tools Are King

I don’t think I’ve appreciated CLI tools enough until right now. The storm of AI tools and helpers are fun to test out, and I’ve done my share of GUIs and web-only portals, but I always felt like I was missing functionality or a way to script into my own flow.

I use Claude Code as my go-to and I use it 99% of the time in the terminal. I have my Neovim setup with my favorite plugins so I can easily view my open PRs and even do full reviews with Octo (freaking amazing plugin, had to shout it out). And just the other day I created a CLI tool with Go to search logs and traces from the terminal. Badabing badaBOOM!

Now you might be wondering, that’s cool and all but when the hell would I need to look at text-only versions of everything? All my pretty colors and buttons are gone and missing!!

Well, have you thought about how your friendly neighborhood AI tools are actually the COMPLETE OPPOSITE?? They want text, love text actually, for their context and solving your problems. You can of course give it some HTML or some Claude-in-Chrome beta permissions, but those are honestly pretty bad, let’s be honest. All you need is a CLI tool that already bypasses all the fluff, gives you the context and data that you want, and feeds it to your AI to make all the right decisions. It’s smooth sailing baby.