If you've been paying attention to the Cloud Code ecosystem at all, then you've noticed a huge shift.
Everyone, I mean everyone, is building CLI tools to enhance what Cloud Code can do. And today, I'm gonna show you my 10 favorites, and they range from YouTube research to deploying applications
to controlling my entire Google Suite,
all from Cloud Code. And you might recognize a few of the ones we cover today, but if you leave with just a couple new ones,
then I'll have done my job. So the first tool on our list is kind of a meta pick, and that is CLI Anything. This is a CLI tool that creates other CLI tools. This thing is completely open source and it's from the makers of LightRag and Rag Anything. So these guys are kind of titans in the AI open source world. Now the sell for this particular tool is that I can use CLI anything and point Cloud Code at any open source project.
And Cloud Code will use CLI anything to create a CLI tool for said program. And this repo shows some of the projects that they've already done this on. Things like GIMP, Blender,
InkSpace,
OBS, Zoom. We actually did a full deep dive on this exact tool not too long ago. So I'll put a link to that above. And it looks like they've added a few since that NotebookLM
as well. Right? So the idea is if you want Claude code to work with some other program from the terminal and there's not like a clear API type deal to go along with it and it's open source, well, this is the perfect tool for that job. And it's also really easy to install and use. It's like two steps to install it, and then it's just a one step process to actually execute this. It runs the full pipeline on its own. And for you, the user, it's very, very simple. So before we jump into tool number two, a quick word from everybody's favorite sponsor,
me. I just released the Claude code masterclass.
You can find it inside of chase.aiplus.
There is a link to that in the pinned comment. And it is the perfect place if you're trying to figure out how can I go from zero to AI dev, especially if you don't come from a technical background?
I add updates to this every single week, and we really focus on real life practical use cases, not just feature explanations. So if that's something you're interested in, definitely check it out. And if you're brand new, I also have the free Chase AI community.
Tons of free resources.
Link to that is in the description, so hopefully there's something there for everybody. Now tool number two is one of my personal favorites and you've seen me showcase this before and that is the notebook l m dash pi tool. This tool, this CLI tool allows us to connect Cloud Code to NotebookLM.
There's no public API for NotebookLM. So there's no way normally for me to control NotebookLM
from the terminal unless I've created some sort of custom browser automation.
But this GitHub repo
fixes that, and this is something I quite literally use every day for my own research because it solves one of the issues with Claude code and Sonnet and Opus in general. It's the fact that they can't really handle videos.
NotebookLM can. I can just throw YouTube URLs at NotebookLM.
It will do all the analysis for me for free because these tokens are on Google servers, not ours, and then it just brings it back to Cloud Code. And on top of the analysis it does in Notebook LM, it can create all the deliverables that Notebook LM does as well. So things like podcasts,
videos, slide decks, infographics,
quizzes, flashcards,
on and on and on. If you can do it in Notebook LM,
you can do it inside of Cloud Code. And being able to control all of this from a terminal is a huge benefit versus doing it manually inside of NotebookLM. And it's not just a convenience thing.
It's the fact that I can very easily take all the analysis from NotebookLM
and integrate it into whatever I'm doing at a larger scale inside of my projects. And you also get access to things you can't really do inside of Notebook LM's web interface. And they're all listed down here, everything from
batch downloads to slide revision to programmatic sharing. Now like many of these CLI tools, it's really a two step process because we need to, one, actually install the CLI tool, the dependency on our actual computer. And then number two,
you know, we need a skill. Skills and CLI tools tend to go hand in hand when it comes to Claude code because we need to essentially give it the functionality
and then we need to teach it how to use that specific tool in the specific way. So if we're talking about CLI tools that don't require a skill, I'll let you know. But this is one of them that does. And in pretty much all these repos, there will be some sort of command that you just have to copy paste to get the skills loaded.
And also,
you know, while all the install is spelled out for us here, there is nothing stopping you from just
giving Code the URL to whatever repo we're talking about or, you know, whatever web page happens to explain the CLI,
give it the Cloud Code and it will install it for you. Now I really like tool number three because it's all about money, and that's the Stripe CLI. Now if you've ever used Stripe
to essentially create a product that's tied into something like a web app, you know what a pain in the butt it is to go through Stripe's interface. It is not user friendly at all. However, when we use the Stripe CLI,
it takes all of that turmoil
away from you and puts it on top of Cloud Code, and Cloud Code is able to navigate all that nonsense
much more quickly. That being said, when you are dealing with things that have to do with money and transactions,
like, obviously, you still wanna test these out by hand. But the actual, like, product creation
and all, like, the steps that require you to go through, like, 20 different tabs inside of Stripe, like, we can just get rid of that. This makes it way easier. Now tool number four is also in this content slash multimedia video game, and that's FFmpeg.
And this is a collection of libraries that allow you to manipulate
video and audio and subtitles,
and it actually can be very useful in things like web design. So I was able to create this scrolling animation
on my web page with FFmpeg.
And what it was able to do is it was able to take an entire video that I had created of this keyboard going from, you know, completely together
to, like, completely expanded
and then chop it up into individual frames to turn it into what you see here. And if I had tried to do that manually, it'd be giant pain in the butt. But something like FFmpeg makes this very simple. If I wanted to do a, let's say, an animation on the hero section, let's say I had some sort of image back here and I wanted to loop it, well, I could just give it one video. It can automatically copy the video, reverse it, stitch it. So it gives Claude code a lot of functionality when it comes to manipulating
sort of multimedia, which is, again, it's a place that Claude code out of the box isn't great at, so these CLI tools that can give it some enhanced functionality in those spaces are always welcome. And I also have a full video breaking down how to do this exactly that I'll link above. Now tool number five is one you probably already know about and you definitely should be using. If not, you're way behind. And that is the GitHub CLI.
If we are doing anything where we are writing code and we wanna push to GitHub, there is no reason why we wouldn't just use the GitHub CLI to do this. Right? Anytime where we have some sort of task or workflow that we are constantly doing and pushing to GitHub and anything on the deployment side is probably one of those, we wanna be looking for CLIs to help us do it. And the GitHub CLI,
you really can't ask for anything better. Now like all things Git and GitHub related, Cloud Code is already very spun off on how to do this properly. So when it comes to installing the GitHub CLI and using it, quite literally, you can do that in one sentence. Open up Cloud Code and say, hey. I wanna install the GitHub CLI. It will do it automatically. It's just gonna ask you to authenticate, which is a really simple process where you click a link, you log in to GitHub, and you're all set. And from here, when it comes to pushing code, when it comes to, you know, commits and doing branches and all these things,
you can just do it from the terminal. Now while we're on the topic of deployments, we would be remiss if we didn't talk about tool number six, Vercel CLI. Now I love Vercel because they have a very generous free tier, and their connection with GitHub makes it very simple to essentially create a CICD pipeline just with these two tools. Now installing the Vercel CLI is again very simple,
and this just allows you, like all these CLI tools, to control
some part of the architecture process, the deployment process from your terminal so not switching from tabs back and forth. Now if you're ever wondering, hey. How do I actually use this? Well, you know what I'm gonna tell you. Take this page, copy the whole dang thing, throw it inside of Claude code, and it won't know what to do. Now when it comes to skills with the Vercel CLI, Vercel actually has a ton of skills available for you to give to Claude code. But if we head over here to deployment, they have a specific one for Vercel CLI, and they have a few others that are in the deployment realm, specifically Vercel Deploy and Autoship. But I definitely suggest checking out this page. I'll put a link to that down below as well because they actually have a ton of really useful skills that if you're doing anything like browser automation
as well, um, same thing like design and UI, you definitely wanna take a look at. Now tool number seven is all about the back end, and that's the Supabase CLI. I like Supabase for the same reason I like Vercel. Very generous, free tier, and I can handle both all of my databases
and authentication
from one place from the terminal using this tool. And remember, Supabase is also open source. It was always meant to be a Firebase alternative. So if you wanna run Supabase completely locally, the CLI tool helps you do that as well. Now tool number eight is all about browser automations and giving Cloud Code the ability to spin up its own
instances of Chrome and do things on the web for you. And that's where Playwright CLI comes in. Playwrights
Playwrights CLI is also a great case study when we look at CLIs versus MCPs.
I highly suggest you take a look at the Playwright YouTube account. They have an entire video on this where they compared them head to head. And CLI,
essentially, to do the exact same thing as the MCP server was both quicker and it was, like, 90,000 less tokens. And that's kind of what you kind of see here with all these CLI tools versus their MCP counterparts
even with the changes that ClodgeCode has made when it comes to MCPs where everything isn't just front loaded. So definitely an interesting thing. But the Playwright CLI
is great. If you want an alternative
while we're on the, you know, topic of browser automations,
Vercel actually has its own. Right? So I mentioned that a little bit before. The agent browser skill. So if you don't love Playwright CLI, you can always check out the Vercel alternative. But I highly suggest you start integrating
something like Playwright CLI into your stack, especially if you're someone who builds web apps. Why is that? Because inevitably, we need to test things on the web apps we build, and I don't wanna go into a new tab every single time, you know, go on the dev server, check out the new form myself.
Why don't I just have Cloud Code do that on its own, spin up five Chrome tabs, and just attack it from a bunch of different angles automatically?
Right? This allows us to do that. Like almost all these, there is also the requisite skills we want to install here, and it's just a one liner, and it will automatically
go inside your DocClot folder. Now I will say Playwright in particular actually is pretty deep. There's a whole lot of things you can do with it beyond just, hey, open up Chrome and test out this form submission. So if you're really into browser automation, I highly suggest you kind of dive into this repo and see what's really available to you because it again, these are deep waters when you go into the browser automation stuff. Now tool number nine is a pretty interesting one. I just got introduced to it not too long ago. You might have seen me reference it in my how to run Claude code locally video, and that's LLM
Fit.
This is a CLI tool that allows you when you run it to figure out, well, what local model actually makes sense for my setup? And for most people, that question has a non obvious answer. I mean, if you head to OLAMA and go to the models, like, it's essentially like a never ending list of different things to do and open source is being updated every three seconds.
And so, you know, every single model also has, like, nine different versions of the same model. So it's it's kind of a confusing space, especially if it's not one you hang out in very often. And this project, LLM Fit, essentially solves that issue. And last but not least is GWS,
the Google Workspace CLI tool. This is the CLI tool that allows us to have Claude code control our entire Google Workspace. Right? We're giving it access to our email, our docs,
sheets,
everything.
Right? This is extremely powerful, but this also is the place where you start getting into those security issues. Like, do we necessarily want Code to have access to all our emails? But luckily, it's not too hard to set up the GWS CLI tool in a way where we almost, like, sandbox Cloud Code, and it has, like, shared folders with us, and it only has access to certain emails if we use filters. So there is some wiggle room if you're scared about the security side. But for many people, having Cloud Code have full access to the Google Suite is a big deal. And even if you do give Claude Code access to, say, your Google email,
Google Workspace has something called Armor,
and it's all about dealing with, like, prompt injections and that sort of thing. So there are guardrails in place. We aren't just, like, letting Claude code go off and do whatever it wants. Now this one in particular has, like, a billion
skills. Like, I'm not really exaggerating. Right? So a big part of figuring out how to use this tool
to the most effect is also figuring out which skills make the most sense. Right? Skills aren't a huge context window, you know, drag.
But if you have too many of them, triggering the right one becomes a problem. So this is the kind of repo where what I would do and what I have done when I installed this thing was I essentially pointed Cloud Code at this thing. I created a new directory. I had it clone the whole thing. And then you can have a discussion with Cloud Code and say, hey, like, alright. Now that you have full visibility into how this works and what's going on, what would make the most sense for us to actually, like, install and use. Right? And that's gonna be different for every single person. So that's my list of my 10 favorite CLI tools as of today. Tomorrow, that list will probably change in a week. I'll probably have added, like, three more of them because I wasn't joking about it in the intro. Like, this is the shift. Like, we're moving away from MCPs.
We're moving into CLIs because it just makes sense. Cloud Code lives in the terminal. CLIs live in the terminal. There's no overhead. It's, like, just a straight connection.
It allows Cloud Code to do the most with the least amount of tokens for all intents and purposes. So hopefully at least a couple of these were new to you and you can begin to integrate them into your stack.
So let me know in the comments what you thought. Make sure to check out Chase AI plus if you're interested in the master class, and I'll see you guys around.