WEBVTT

00:00:00.160 --> 00:00:31.300
Claude just released one of the most powerful tools to date. It's a slash command, and it's called slash goal where you give it a task, and it will work for as long as it takes to get the job done without you having to touch anything. In this video, I'm gonna walk you through how you can use this tool. I'm gonna show you the magic behind why this works so well, and I'm gonna give you a real example on how this works. But let's start with what slash goal actually is. In Claude code, when you type in forward slash, a little menu pops up with a list of built in commands. Now these aren't prompts,

00:00:31.540 --> 00:00:48.725
these are tools. Each one is doing something very specific, and slash goal is one of those commands. It's brand new. And let me tell you, it's so powerful that I've been using it for the past forty eight hours straight. So here's the problem that slash goal is solving. Let's say that you have a year's worth of bank statements that are in PDFs,

00:00:48.725 --> 00:02:37.005
and you want every transaction to be pulled out. You want them categorized into things like food and gas and subscriptions and a monthly spending breakdown that you can put into a spreadsheet at the end. That's a big job. Without slash goal, Claude will do it. It does a really good job, but it would pull the transactions from the first statement, and then it would stop. And then it waits for you to type something like keep going. And that keeps happening over and over and over again, and you're just sitting there babysitting your computer for over an hour. Now that's how it used to work, but slash goal fixes that completely. You type in slash goal followed by one sentence describing exactly when Claude Coach should stop, and then Claude just works turn after turn. It's running on its own until the job is fully complete. Alright. So take a look at this. You type in slash goal and then a finish line. A finish line is something that can be verified by Claude. You would type in something like this. Every file in my receipts document has been categorized and summarized into a spreadsheet that exists with totals. That's the finish line. And then Claude just starts running. And you see that little indicator right here? That shows that the goal is active with a timer. That's your proof that Claude is working on its own, and it's not waiting for you. It's not waiting for me. It's just going. But there's something that's really interesting about this. So I wanna talk about why and how this actually works so well. When you set a goal, there's actually two AI agents working at the same time. There's the main model. That's the actual worker. It's using Opus or Sonnet. That's the one that's actually doing the job. It's building the files. It's writing the code. It's organizing your stuff. That's your employee. But the magic, the magic comes in with the second worker. You can think of the second worker like the employee's boss. After every single step that the worker takes, the boss is jumping in. It's reviewing everything that just happened. It's asking one simple question. Is the goal net yet? If the boss says no, then it tells the worker exactly why the job's not done yet, and then it kicks off another turn. The worker goes back to work, and then the boss checks again and again and again, and this loop continues

00:02:37.085 --> 00:04:27.955
until the boss finally says, yes. That is done. It is complete. And that is when Claude will stop. And that's the magic behind slash goal. If you type slash goal with nothing after it, it shows you how long the report's been going. It shows you how many turns. It shows you how many tokens have been used. It's kind of your your dashboard. You can always check-in on your employee. But let's talk about the setup really quick because I think this is really important. If you want the full hands off experience where you actually walk away and come back to a project that is completed, you need to do two things. First is type in slash goal. That's the easy part. We just talked about it. But there's a second thing. The second thing is turning on auto approve. By default, every time Claude wants to run a command or edit a file, it's gonna ask for permission. It's gonna say, can I do this, or can I run that? If you don't turn on auto approve, Claude will pause and then wait for you to click yes on every single action even when slash goal is running. But that's okay. That is a safety feature. But if you want it to run automatically, you need auto approved turned on. Now there are some things to consider here. You are giving AI permission to do everything on its own. The good news here is Claude does have some safety nets built in. Claude's not gonna run anything dangerous without asking you first. It stays within the project that you're giving it, and you can always set limits on what it's allowed to do. I would say that auto mode's a little bit more of an advanced feature, and you should fully understand what Claude has access to and how your data is being handled before you turn it on. So Anthropic has a full security and privacy document. I'll link it in the description. Read it. It's powerful, yes, but you should really be using it responsibly. And there's one more really important thing that we need to talk about in this video because if you get it wrong, slash goal will either run forever, which can waste money or not work or use all of your tokens. And trust me, I've already burned through a day's worth of tokens on one task, and I learned the hard way. But I'm here to show you what that is so you don't have to learn the hard way. Remember the boss? The boss can only see what the worker tells it. It can't go check your files on its own. So your goal condition, your finish line, has to be something that the boss can confirm

00:04:27.955 --> 00:04:57.665
just with what the worker has reported back. It can't be something vague. You can't say make no mistakes or do a good job. Those are real examples that I've tried, and the boss just has no way to confirm them. It's too vague. So Claw just spins in a circle and using tokens every single time. For example, you do not wanna say, clean up my files and make everything organized. How does the boss know when everything's organized? It doesn't. It's too vague. So Claude will just keep going and going and going, and it won't stop. And it'll use all of your tokens, or if you're using your API,

00:04:58.150 --> 00:05:19.035
even real money. Instead, you would say something like this. Every file in my receipts folder has been renamed with the date and the vendor name. It's categorized in the monthly folders, and a spending CSV exist with one row per receipt. You see the difference there? The second one has a finish line that the boss can actually verify. It's a specific file that needs to exist, a specific

00:05:19.515 --> 00:07:29.030
folder that needs to be created, something that the boss can look at in the conversation and say, yes. That is actually done. And there's one more thing. You could always add a safety cap. At the end of your condition, you can always say something like, stop after 30 turns or stop after forty five minutes. That is your seat belt. If something goes wrong, Claude is going to stop instead of running all night and burning through all your credits. You always wanna do this every time. Trust me. You wanna add that safety net. Hey. Before we get started with the demos, if this has been helpful so far, please subscribe, like the video, leave a comment. It's something that will really help out my channel, and, of course, I would really appreciate. But let's get to some real demos. Okay. So let's say that you own a pizza shop. You know that you need to be posting on social media every single day, but you don't have the time to do it. You don't have the time to plan it or write it or come up with ideas every single day. And I think most small businesses are like that. They know they have to do it, but it takes forever to create those. So if we were gonna use the goal command, I would say slash goal and then give it a detailed finish line. Take a look at this one. It's basically asking Claude to build a full week of social media content for this piece of shop with captions and hashtags and real images that's gonna pull from my Nano Banana API, and it's gonna put it all in a professional PDF for me to use. And if it's not done in 20 turns, it's going to stop. And, of course, the boss is making sure that all 15 posts are there with images before it signs off. And this is what it looks like. We have a full week content here, 15 posts, three platforms, every caption written, the hashtags, the images, everything is there. I didn't have to do a single thing besides type in that prompt, and then I came back, and here it is. This kind of thing right here is what a social media manager would charge hundreds of dollars a month to do, and that's just one example. You could use slash goal to build a loyalty program for a dog grooming business or plan a full month of daily specials for a coffee shop or write a personalized response to every single review. You could generate invoices for all of your clients. Anything that takes multiple steps and takes a lot of time, you can use slash goal to handle it. Now before you run this thing, uh, let's talk about cost. First, you do need a pro or max plan. So slash goal can get expensive if you're not careful. Like I mentioned before, the boss keeps Claud running until the job is done. But if your condition is bad, the boss will never be done. It'll never be satisfied,

00:07:29.110 --> 00:08:22.885
and Claud will just keep going and going through a loop and using your tokens. Now there are three rules here to help avoid this. Number one, always use that safety net. Again, you can say stop after 25 turns or stop after forty five minutes. Number two, check your usage before you walk away. You can always type slash usage and see where you're at with your credits. And number three, start small. You don't need to set your first goal to reorganize your entire business. No. You wanna start with one folder. You wanna do one batch of receipts or one set of reviews. You wanna get comfortable with it and then scale up. If you do those three things, you should be in a good spot. But that's slash goal. You set a finish line. Claude's gonna work on its own. The boss is gonna watch over everything until the job is done. If you feel comfortable, turn on auto approve. If you don't, then don't turn it on. You're gonna write a specific condition with the safety cap and then let Claude do all of the work. Now a quick plug. If you haven't seen my claw design video, you can check it out here. I encourage you to do so. And if this helped, leave a like. Please subscribe, and I will see you in the