WEBVTT 00:00:00.000 --> 00:00:02.560 In the month of May, I did 318 00:00:02.560 --> 00:00:03.520 commits 00:00:03.760 --> 00:00:05.040 with Cloud Code. 00:00:05.280 --> 00:00:16.765 Now I did have some with some of the other ones, like, used a little bit of codecs, root code, and augment code, but the vast majority of my commits and the vast majority of the number of lines of code that I produced or 00:00:17.085 --> 00:00:19.325 refactored came from Cloud Code. 00:00:19.565 --> 00:00:21.405 It is phenomenal. 00:00:21.725 --> 00:00:25.405 When I first started using Cloud Code back when it came out, 00:00:25.805 --> 00:00:28.045 I actually liked it back then too. It was early, 00:00:28.560 --> 00:00:34.000 but it had cost way too much money for me to be able to justify using this on a daily basis. 00:00:34.480 --> 00:00:35.680 Now Cloud Code, 00:00:35.920 --> 00:00:38.400 it's a CLI based coding assistant 00:00:38.560 --> 00:00:46.345 that is really locked into the Anthropic ecosystem. So it's important to note, I'm a little bit nervous about being locked into ecosystems, 00:00:46.505 --> 00:00:53.785 which is why I still really use and really love RootCode. And I think open source really is where I wish things like this would actually be. 00:00:54.105 --> 00:00:58.505 But I think there's something to argue with how good CloudCode actually works 00:00:58.880 --> 00:01:02.160 and the fact that they can give you this monthly fee 00:01:02.400 --> 00:01:04.800 to allow you basically unlimited 00:01:04.960 --> 00:01:06.240 unlimited use. 00:01:06.400 --> 00:01:10.560 So for OS support, this is what's a big problem for me and still is today. 00:01:11.085 --> 00:01:14.125 So they out of the gate support Linux and Mac. 00:01:14.605 --> 00:01:15.245 Now 00:01:15.645 --> 00:01:25.405 the reason that this is a problem for me is I am primarily a Windows user, and I know a lot of you would be like, why? Why are you using Windows? 00:01:25.405 --> 00:01:25.885 And 00:01:26.250 --> 00:01:28.170 part of the problem with that is 00:01:28.410 --> 00:01:38.090 when I started programming years ago, I started in the game industry. And everything you do in the game industry with Windows based, that's just become kind of my native operating system. 00:01:38.575 --> 00:01:44.655 And on top of that, I actually do games, so there is a dual purpose there. So I I do have a Mac. 00:01:45.055 --> 00:01:49.775 I do dual boot Linux. I have a Linux computer to my right, but I prefer 00:01:49.855 --> 00:01:55.220 working on a Windows computer. I know that is not normal or popular, but that is what I prefer. 00:01:55.780 --> 00:02:02.260 So what I end up having to run for Windows in particular is I actually have to run WSL. 00:02:02.500 --> 00:02:03.940 Now WSL, 00:02:04.420 --> 00:02:06.100 it's actually gotten a lot better, 00:02:07.775 --> 00:02:20.975 And I'm actually using Ubuntu with WSL. I know some people use Debian or some other flavors of it, but Ubuntu has been really good to me. And I can do 80 to 90% of everything that I need to with WSL, 00:02:21.460 --> 00:02:28.180 and I have enough RAM and system resources to where that doesn't actually matter. So I'm just calling that out. If you are a Windows user, 00:02:28.820 --> 00:02:36.820 you are going to probably have issues unless you are willing to set up WSL, and I know some people are resistant to that. So that's just worth noting. 00:02:37.645 --> 00:02:40.765 Now on the pricing side, as I was putting together this video, 00:02:41.005 --> 00:02:53.950 I actually saw that Kat Wu posted this. You can now actually use Clogcode a little bit on the pro plan. So what does that actually mean? We've got the pro plan at $20 a month. Now this plan is what I was on for the longest time. 00:02:54.430 --> 00:02:58.030 And this is typically for users that are just working in the web UI, 00:02:58.270 --> 00:03:01.630 but now you can actually come in and at least try out Cloud Code. 00:03:02.030 --> 00:03:06.735 I'd recommend doing this. This is a massive, massive thing for them. 00:03:07.375 --> 00:03:14.735 What kind of limits you get? I bet they're gonna be very tight, to be honest with you. So I wouldn't expect to be able to do a lot, but you can at least see how it works for you. 00:03:15.215 --> 00:03:17.535 Then they have a $100 a month plan, 00:03:18.390 --> 00:03:21.030 and this is the max five x plan. 00:03:21.590 --> 00:03:22.630 I've actually 00:03:22.950 --> 00:03:26.390 just switched to this for this upcoming month because 00:03:26.390 --> 00:03:33.190 I really do wanna be able to use some of my other coding assistance a bit more and not feel like I'm paying $200 a month 00:03:33.855 --> 00:03:36.415 and I have to use ClawCode. 00:03:36.575 --> 00:03:38.015 I do love it, though. 00:03:38.495 --> 00:03:46.415 And I if I wasn't in the position that I'm at where I wanna test a bunch of different coding tools and things like that, the $200 00:03:46.440 --> 00:03:57.880 max, I think it what is it? 20 x or 10 x? I can't remember exactly. But it's some x in here. I never hit a single limit on it, and I literally was running multiple instances of clogged code. So 00:03:58.360 --> 00:04:02.255 just something to note here, these plans are phenomenally 00:04:02.255 --> 00:04:02.975 priced. 00:04:03.215 --> 00:04:05.935 Because when I was early on using Cloud Code, 00:04:06.175 --> 00:04:07.775 I would burn $20.30 00:04:07.775 --> 00:04:09.215 dollars in a day, 00:04:09.855 --> 00:04:17.650 and that wasn't even me, like, aggressively using it, just using the API. So just noting that that it's probably worthwhile considering 00:04:17.890 --> 00:04:22.290 jumping up to the $100 a month plan if you find yourself liking CloudCode. 00:04:22.610 --> 00:04:25.090 But try it out on the $20 a month plan 00:04:25.330 --> 00:04:26.130 because 00:04:26.210 --> 00:04:32.045 this is an exciting exciting update for the people that haven't had a chance to test it out yet. 00:04:32.445 --> 00:04:35.565 Alright. So jumping over to the next topic here that I wanna talk about, 00:04:35.965 --> 00:04:37.565 and this is one that 00:04:37.725 --> 00:04:43.245 kind of threw me off a bit when I first were getting going, but I've come to really appreciate it. 00:04:44.240 --> 00:04:44.880 And 00:04:45.120 --> 00:04:48.320 that's really that prompting matters a ton. 00:04:49.040 --> 00:04:52.240 So you can actually guide Claude 00:04:52.240 --> 00:05:01.705 to I d ideate with you. You can guide Claude to think very hard Claude code, to think very hard about something. I work very hard about it or make a checklist. 00:05:02.105 --> 00:05:08.825 And it's just all about how you prompt it. So a few things that really changed it for me, and I'm not lot of you probably know this already, 00:05:09.065 --> 00:05:11.865 but I literally will type in ultra think 00:05:11.865 --> 00:05:13.490 about this thing, 00:05:13.810 --> 00:05:16.610 whatever it is, and implement the following. 00:05:17.250 --> 00:05:19.250 You can also do things like architect, 00:05:19.250 --> 00:05:20.050 plan, 00:05:20.130 --> 00:05:20.610 and 00:05:21.090 --> 00:05:21.810 implement 00:05:22.210 --> 00:05:23.250 the following. 00:05:23.410 --> 00:05:25.650 Things like that make a huge difference 00:05:26.205 --> 00:05:29.005 in, like, getting it to do what you want it to do. 00:05:29.725 --> 00:05:40.125 And you don't have to use UltraThing because sometimes you may just want something basic to be done. So you just say, you know, do this thing. You can also say, don't write any code. I want to ideate with you. 00:05:40.890 --> 00:05:43.530 And this is important because, uh, 00:05:43.690 --> 00:05:48.010 what you wanna do in certain cases is think through a plan and kinda figure things out. 00:05:48.410 --> 00:05:51.850 I typically use augment code for this, just to be totally honest. 00:05:52.090 --> 00:05:59.875 But I have found myself doing this more and more with Cloud Code because I find that that is just it's actually pretty good at it at times. 00:06:00.595 --> 00:06:03.315 The other thing that's really interesting is REPL. 00:06:03.715 --> 00:06:07.395 And so, basically, what you can do is you can do something like, um, 00:06:07.635 --> 00:06:08.435 tell me 00:06:09.075 --> 00:06:10.915 tell me about my code base. 00:06:12.020 --> 00:06:13.940 And it will create, 00:06:13.940 --> 00:06:17.780 like, a read, evaluate print loop. It's what REPL stands for. 00:06:18.340 --> 00:06:22.500 And it does a really, really good job answering 00:06:22.500 --> 00:06:24.980 kinda context 00:06:24.125 --> 00:06:25.405 specific questions. 00:06:25.565 --> 00:06:27.965 Try it out, especially if you're using the pro plan. 00:06:28.205 --> 00:06:30.525 I was very impressed with its ability 00:06:30.765 --> 00:06:33.725 to pick up context of your code base. 00:06:34.125 --> 00:06:35.725 And it gets better 00:06:35.965 --> 00:06:40.125 if you run the init command and create a cloud dot m d file. 00:06:40.730 --> 00:06:43.050 And this is something that you can keep up to date. 00:06:43.770 --> 00:06:49.530 But, basically, what claud will do is go through your code base and build it so sort of, like, information, 00:06:49.850 --> 00:06:57.115 kinda like a map of your code base that it can then use. What's also interesting about this is it will search for other, 00:06:57.275 --> 00:06:58.715 uh, AI tools 00:06:58.875 --> 00:07:15.210 and see how you prompted those. So it'll say, like, do you have GitHub Copilot instructor? Because I found mine when I was doing it, and it kinda built, uh, used some of that stuff. It searches for, like, cursor rules and so on. So it knows about the other files that it's looking for there when it's when it's kinda building out that rule set. 00:07:15.690 --> 00:07:19.770 So I would I would learn to talk to it in the way that works for you. 00:07:20.615 --> 00:07:24.695 I I started out thinking that I needed to be, like, very specific. 00:07:25.095 --> 00:07:30.695 So I was like, you know, you basically you can use at to go, like, chat.ts.vu, 00:07:30.855 --> 00:07:32.615 and then you can tab into 00:07:33.095 --> 00:07:34.455 to kinda complete that 00:07:35.110 --> 00:07:39.990 so that it picks the reference to that file. And I would say change this specific thing. 00:07:40.950 --> 00:07:41.670 And 00:07:41.910 --> 00:07:45.110 it's really, really good when you do this. 00:07:45.430 --> 00:07:51.105 And if you got a high enough level or a strong enough level understanding of your code base, 00:07:51.425 --> 00:07:54.785 this is the quickest way to get things done in your code. 00:07:55.265 --> 00:07:57.745 But you can also be very vague. 00:07:58.465 --> 00:08:01.425 And this is the thing that surprised me the most because 00:08:01.860 --> 00:08:04.180 its REPL loop does 00:08:04.900 --> 00:08:09.940 pretty dang good at figuring out what it needs to do. So I can say something like, 00:08:10.420 --> 00:08:13.140 you know, in my orchestrator mode, 00:08:13.780 --> 00:08:16.420 I want to add a new tool, 00:08:17.525 --> 00:08:19.525 blah blah blah. So, 00:08:19.525 --> 00:08:23.045 basically, I'm not giving it files. I'm just saying go do it. And, 00:08:23.605 --> 00:08:25.125 know, 80% of the time, 00:08:25.685 --> 00:08:27.605 it'll find what it needs to and 00:08:28.645 --> 00:08:31.125 make some good, uh, good changes there. 00:08:31.940 --> 00:08:36.020 The other thing that I would say is it's important, uh, on the prompting side 00:08:36.260 --> 00:08:40.580 to not be afraid to, uh, to kind of start over. 00:08:41.460 --> 00:08:47.140 Because sometimes you prompt it, and you realize when you reread it that you were too vague. 00:08:47.595 --> 00:08:54.075 Or, actually, it answered the question, but you had meant something different. Because a lot of times I get busy, and I'm like, oh, no. No. No. No. 00:08:54.555 --> 00:08:55.675 And 00:08:55.675 --> 00:09:03.630 I looked back over there. I'm like, oh god. I woulda had no idea. I'm surprised it actually got as far as it did. So don't be afraid to start over and just revert and do it again. 00:09:04.910 --> 00:09:17.795 Uh, because a lot of times, I find that people feel like they have to keep grinding in the same direction, but don't do that. Like, get rid of it and and start over. So now what I wanna do is I wanna go through some tips that I've learned 00:09:18.195 --> 00:09:22.675 that have actually really helped me a lot with, uh, using Cloud Code. 00:09:23.075 --> 00:09:34.260 The first thing is if I want to do something like I kick off a task let me do that right now. So in this one, I'm actually going to ask it to ultra think through refactoring a file. 00:09:34.580 --> 00:09:38.100 I can also type in stuff while it's syncing. Please make sure 00:09:39.060 --> 00:09:40.740 all functionality 00:09:40.820 --> 00:09:41.940 remains intact. 00:09:42.445 --> 00:09:44.365 Also, make sure that 00:09:44.685 --> 00:09:47.085 you break out components 00:09:47.085 --> 00:09:48.285 when possible. 00:09:48.525 --> 00:09:56.685 So you can send it messages while it's thinking. This is something that's very it's kind of an awesome feature that I didn't know about 00:09:57.100 --> 00:10:00.300 until a few days after they release it. It's a fairly new feature. 00:10:00.620 --> 00:10:03.340 But it's worthwhile knowing that this exists because 00:10:03.580 --> 00:10:06.300 it will allow you to think about, 00:10:06.700 --> 00:10:10.860 oh, I should have told it this. And now you can actually send it, and it'll do a good job 00:10:11.285 --> 00:10:19.445 kind of pushing that in. The other thing that I would say is don't immediately just go to yes and don't ask again in the session. 00:10:19.685 --> 00:10:20.645 Make sure 00:10:21.125 --> 00:10:23.765 you're comfortable with the direction that it's going 00:10:24.140 --> 00:10:31.420 before you kick that off. Um, and then use this no and tell Claude what to do differently a lot. 00:10:31.820 --> 00:10:50.745 This has saved me so many times when it is unclear or going away that I don't like. I'll say something like, no. I'd rather you focus on a different part. You know, this this is all too vague right now, but you get what I'm saying here. It's like you can actually redirect it if it's going going awry there. 00:10:51.065 --> 00:10:56.680 Then I just wanna be like, alright. I'm gonna clear this. Let's get get rid of that. We're starting over with a new context here. 00:10:57.560 --> 00:11:04.920 So you can also use at to get a list of files. So I can see if you hit at here and I start typing chat.ts.view, 00:11:05.000 --> 00:11:07.320 I can hit enter, then the path will be 00:11:08.455 --> 00:11:11.815 be filled in there. So in this in this query here, 00:11:12.215 --> 00:11:14.615 I'm telling it in a particular file. 00:11:14.775 --> 00:11:16.295 I'm telling it the problem. 00:11:16.775 --> 00:11:25.690 In this case, I don't have an idea what the prob like, how to actually fix it, so I'm asking it to give me ideas on how to fix it. And because I've directed it into that file, 00:11:25.930 --> 00:11:36.330 it's going to be a lot better at helping track down that problem there. So that's a it's something that highly, highly recommend that, and it's really, really helpful if you know 00:11:37.095 --> 00:11:39.415 the area of the code that you wanna work in. 00:11:39.655 --> 00:11:43.335 But you don't have to be that specific on it. You can be very 00:11:43.735 --> 00:11:50.535 vague, but you should also be kind of specific too if possible. So you can be you can target functions. You can target files. 00:11:50.970 --> 00:11:56.490 You use things that are greppable or searchable. It's really good at that, very similar to the way Codex works. 00:11:57.050 --> 00:11:59.130 And so in this case here, 00:11:59.530 --> 00:12:08.645 uh, it's adding some debugging logs because it doesn't really know it's trying to get some information on it. I think this is fine. I'd probably accept this and kind of continue on there. 00:12:09.125 --> 00:12:21.440 But if I if I want to be super vague on it so here, I'm gonna ask it, can you walk me through writing code about how to add a new tool like multi image? But this time, I want it to be search and replace for brief chat. 00:12:21.680 --> 00:12:23.360 Now what this is going to do, 00:12:23.680 --> 00:12:28.400 I didn't give it a file to start in. I did give it some things that are greppable, 00:12:28.400 --> 00:12:32.480 but I wouldn't even have to do that. It usually will do a pretty good job finding it. 00:12:32.800 --> 00:12:35.040 And I've actually tested this prompt a few times, 00:12:35.675 --> 00:12:41.675 and this one actually will return really, really good results. So if I take this same prompt here, 00:12:43.275 --> 00:12:46.475 and I'm going to open up AugmentCode over here on the right, 00:12:47.355 --> 00:12:52.900 and you can see some of the stuff that I do in there. I'm gonna put it in chat mode, and I'm just gonna say, 00:12:54.020 --> 00:12:55.620 basically the same question. 00:12:57.060 --> 00:13:03.300 And we're gonna take a look at kind of what it comes up. So this one at said to create a new search replace tool handler, 00:13:03.755 --> 00:13:05.115 which is awesome. 00:13:05.595 --> 00:13:09.515 And, yep, that's exactly what it's talking about here. It's a very, very similar 00:13:09.755 --> 00:13:12.875 similar response. It's very, very snappy for each. 00:13:13.275 --> 00:13:15.515 So for this longest time, 00:13:16.290 --> 00:13:20.930 I actually just kind of the first couple weeks I used Cloud Code, I kind of ignored 00:13:21.330 --> 00:13:24.450 its ability to pick up context of my code base. 00:13:24.850 --> 00:13:28.130 Don't do that. Like, if you're not paying for Augment code, 00:13:28.795 --> 00:13:30.555 Cloud Code does a really, 00:13:30.955 --> 00:13:32.395 really good job, 00:13:32.635 --> 00:13:34.955 uh, getting context of your code base. 00:13:35.355 --> 00:13:38.235 And whatever they're doing under the hood here is incredible. 00:13:38.555 --> 00:13:42.395 So that that's kind of just some of the tips that I picked up kind of running through this. 00:13:43.160 --> 00:13:44.920 Now on the command side, 00:13:45.640 --> 00:13:49.960 there's only a few that I think are, like, very important. The omit one we talked about, 00:13:50.520 --> 00:13:52.120 I'd recommend trying this. 00:13:52.520 --> 00:13:58.600 It's impressive the what it puts together, and the CloudMD file does help, uh, in my experience. 00:13:59.025 --> 00:14:01.105 On an existing code base, it does help. 00:14:01.585 --> 00:14:02.225 Now 00:14:02.465 --> 00:14:16.190 what this will do is this will actually generate a Cloud dot MD file, and I can show you some examples of that here in a minute. I'll actually pull over to to Versus Code and just run this in my one of my repos. I've cleared it out already. I'll show you what that looks like. 00:14:16.910 --> 00:14:21.150 Now the other command is clear. This is one that's very important 00:14:21.470 --> 00:14:24.270 because there's sometimes you're just done with the 00:14:24.525 --> 00:14:30.765 you're done with the context that you're in. So, like, wipe it out and start a new context. Don't keep it going forever. 00:14:31.085 --> 00:14:34.765 Don't be like one of the people that keep a chat window going forever 00:14:35.165 --> 00:14:39.380 and don't realize that you should just clear your context. So clear it When you're done, 00:14:39.860 --> 00:14:40.980 there's also 00:14:41.860 --> 00:14:45.620 models. So you can actually switch switch what models are active. 00:14:46.020 --> 00:14:55.380 This can be things like Opus or Sonnet four. Sonnet four is what I run on a daily basis. I very rarely switch to Opus because that eats into my limits 00:14:54.255 --> 00:14:55.695 very, very highly. 00:14:56.815 --> 00:14:59.855 The other thing that they have is they have a compact command. 00:15:00.095 --> 00:15:01.695 This is one where 00:15:02.015 --> 00:15:09.455 it will it will auto run for you. You don't really need to worry about this a lot of times, so you can just let this kinda do its thing. Right? 00:15:10.630 --> 00:15:12.230 If you are running 00:15:12.470 --> 00:15:17.110 via the API, there is, like there's a cost command and there's a status command, 00:15:17.350 --> 00:15:20.230 and then all the normal ones, like log in and log out. 00:15:20.950 --> 00:15:24.950 These are the ones, if you're just getting started, that you should just get comfortable with, specifically, 00:15:25.455 --> 00:15:28.735 a net clear, checking your or changing your model, 00:15:28.975 --> 00:15:29.855 compacting. 00:15:30.255 --> 00:15:39.960 Beyond that, everything else becomes kind of advanced and awesome. Right? Like, things that you can run a cloud code via a deploy pipeline. 00:15:40.200 --> 00:15:44.040 So you can or you could have it set up so that it runs 00:15:44.440 --> 00:15:54.245 on where with no input. So just auto runs for you. So there's a lot of, like, really advanced stuff you can do, which I've been playing around with. And I think it's important just to keep that all that in mind. 00:15:54.885 --> 00:15:59.365 Now orchestrating tasks, this is something that I actually really 00:15:59.765 --> 00:16:01.125 am excited about. 00:16:01.685 --> 00:16:03.685 Because we have a CLI tool, 00:16:04.220 --> 00:16:08.380 if you think about it, it becomes very easy to specifically 00:16:08.380 --> 00:16:10.860 take and send out bite sized jobs. 00:16:11.100 --> 00:16:15.260 And so in root code, what I actually did is I created a, uh, 00:16:15.420 --> 00:16:17.180 a clog code mode 00:16:17.945 --> 00:16:20.425 that literally would break out tasks, 00:16:20.825 --> 00:16:22.985 and it would send CLI command 00:16:23.625 --> 00:16:24.665 to clog. 00:16:25.465 --> 00:16:26.105 And 00:16:26.425 --> 00:16:36.530 this is great, and it works great some of the time. I honestly found it more kind of a pain than anything trying to it go between root code and, uh, cloud code. 00:16:36.930 --> 00:16:40.210 But there are tools starting starting to pop up where you can 00:16:40.530 --> 00:16:43.090 manage multiple cloud code instances. 00:16:43.250 --> 00:16:47.705 One of the problems I run into a lot of times, a lot of them don't support WSL very well. 00:16:48.185 --> 00:16:56.665 So, again, when I have to go over to Linux to try them out. But I do locally the way I do a lot of orchestrating of tasks. I do that with Git Worktrees. 00:16:57.660 --> 00:17:02.780 And git work trees is something that's actually really, really, really powerful. 00:17:02.940 --> 00:17:07.020 Or, I mean, simply, you can actually just, uh, run multiple instances. 00:17:07.740 --> 00:17:27.855 I've never ran into an issue having two or three instances running at a time, and I typically run them in the terminal window of my Versus Code. So it's just all right there. I know some people might prefer to run that outside of Versus Code, but I I'm traditional IDE guy. I like it being a Versus Code. It just it's so nice having it integrated in there very well. 00:17:28.700 --> 00:17:30.540 On the Git Worktree side, 00:17:30.780 --> 00:17:33.580 what it typically does is you can actually 00:17:34.060 --> 00:17:36.940 set up sort of, like, feature branches 00:17:37.340 --> 00:17:41.580 in sort of this tree structure. So there's these things like Git Worktree 00:17:42.005 --> 00:17:42.885 add. 00:17:43.205 --> 00:17:49.845 Right? So you can do git work tree. You can list them. You can do git work tree. I think it's remove. 00:17:51.125 --> 00:18:00.270 There's some other commands too. I think prune is one. I'd have to go through and and look at all of them. So what you do here is you go git work tree add. 00:18:00.670 --> 00:18:05.150 Here's your path to where you wanna add it to have the the repository 00:18:05.150 --> 00:18:06.430 sort of synced to, 00:18:06.750 --> 00:18:09.230 and then this would actually be your branch. 00:18:10.535 --> 00:18:15.015 And now you can just c d into that path 00:18:15.335 --> 00:18:16.695 and run plot. 00:18:17.895 --> 00:18:22.215 And I can run that and have multiple instances working on different feature branches 00:18:23.220 --> 00:18:24.900 very, very easily, 00:18:25.780 --> 00:18:33.300 and then just switch over to the run them. I still run into the same issues that I have locally with my other type of multi 00:18:33.460 --> 00:18:40.765 agent systems, which is I have a I have a server that needs to be booted up, and this is kind of, uh, 00:18:41.005 --> 00:18:41.725 probably 00:18:42.525 --> 00:18:52.010 kind of whining more than anything. But, basically, I have to stop and start the server when I switch between those instances. So it's not the most ideal thing, 00:18:52.410 --> 00:18:53.690 uh, where, ideally, 00:18:54.010 --> 00:18:56.170 I have that could be a little bit quicker 00:18:56.330 --> 00:19:04.495 for me to actually be able go in and test it. It's again, it's just me kinda whining about it more than anything. So on the impression side, I just wanna say it's very positive. 00:19:04.815 --> 00:19:08.175 I have very few negative things that happen. 00:19:08.495 --> 00:19:11.855 What I will say on the negative side 00:19:12.175 --> 00:19:13.935 is there are times 00:19:14.560 --> 00:19:17.440 that you end up with situations 00:19:17.760 --> 00:19:19.040 where, um, 00:19:19.360 --> 00:19:20.160 spacing 00:19:20.160 --> 00:19:21.520 or merging 00:19:21.680 --> 00:19:22.400 or 00:19:23.040 --> 00:19:25.680 weird states you get into it 00:19:26.000 --> 00:19:27.520 where you can't 00:19:27.705 --> 00:19:42.230 get clogged code to fix it, you're better off just nuking it or going into manually fixing it. Trust me, I've spent enough time with clogged code now to basically be able to pick up instantly when it's in a position where it's not gonna get out of it. Sometimes 00:19:42.230 --> 00:19:43.030 it's 00:19:43.110 --> 00:19:47.830 it's just simple with, I know this just gets on the but tabs versus spaces, 00:19:48.470 --> 00:19:49.270 it will, 00:19:49.830 --> 00:19:57.725 uh, get into a state where it just can't merge things because it's trying to do one or the other, and it just is really weird. It's very rare that these things happen. 00:19:58.365 --> 00:20:10.205 But, again, it's just you'll you'll pick it up as you use it that if as long as you're committing and you're keeping the progress of things you're working on well enough, you're not gonna feel bad reverting whatever change it's got 00:20:10.800 --> 00:20:12.880 or go in and help it sometimes. 00:20:13.200 --> 00:20:16.720 Uh, but on the positive side, it is just fun. 00:20:17.120 --> 00:20:20.880 Like, I'm not kidding you about how much fun it is to use. 00:20:21.120 --> 00:20:21.360 I 00:20:22.000 --> 00:20:22.480 it's 00:20:23.120 --> 00:20:25.280 everything about it just exudes 00:20:26.105 --> 00:20:26.905 fun. 00:20:26.905 --> 00:20:27.385 And 00:20:27.945 --> 00:20:33.785 I know it's it's coding, and a lot of people would be like, uh, why is that fun? But it really is. I 00:20:34.345 --> 00:20:36.185 I feel like it's 00:20:36.825 --> 00:20:39.785 so good at what it does, and there's so much 00:20:40.740 --> 00:20:43.540 nuance to how you kind of guide it 00:20:44.020 --> 00:20:44.740 that 00:20:45.060 --> 00:20:47.700 you feel like you have control of it. 00:20:48.100 --> 00:20:50.340 Whereas some of the other AI agents, 00:20:50.660 --> 00:20:52.180 you have some control, 00:20:52.260 --> 00:20:55.860 but not to the point that clog code is. I don't need to change modes. 00:20:57.195 --> 00:21:00.875 I basically just guide it based on how I prompt it to behave 00:21:01.115 --> 00:21:03.435 from this ultra hardcore, 00:21:03.755 --> 00:21:07.195 like, really deep thinker, task list creator, 00:21:07.275 --> 00:21:10.955 all the way down to, I just wanna talk to you about an idea that I've got. 00:21:11.620 --> 00:21:17.460 And there's all the variance between there that just makes you feel like you have control over this agent 00:21:17.700 --> 00:21:19.540 unlike other agents. 00:21:20.100 --> 00:21:20.740 And 00:21:21.060 --> 00:21:24.260 you may find that you can just reword a problem 00:21:24.580 --> 00:21:25.300 that 00:21:25.460 --> 00:21:30.755 other agents have trouble with, and you word it in such a way with ClawCode, and it'll freaking nail it. 00:21:31.475 --> 00:21:35.235 The other thing that I wanna say from the impression side is 00:21:35.395 --> 00:21:38.835 that it's fast. Like, it it is 00:21:40.035 --> 00:21:42.755 never it never feels to me like it's a slog. 00:21:43.380 --> 00:21:47.620 So a lot of times, you know, with some of the other agents, especially GitHub Copilot, 00:21:47.780 --> 00:21:54.500 one of my big complaints about that is how slow it is. It it literally takes, like, triple the time some of these other agents. 00:21:54.820 --> 00:21:56.420 But Cloud Code is fast. 00:21:57.045 --> 00:22:17.310 You can make it faster, and you can make it slower by how you prompt it, which is also what I love about it, which goes back to sort of the control that you have over it. Um, until you use it, you really would have a hard time understanding what I'm saying about that. But it is it is a real thing that I feel. I'm jumping over into Versus Code because I wanted to show you what this looks like in practice here. 00:22:17.550 --> 00:22:21.390 So the first thing that I would do is you can see here that I've been working with ClawCode 00:22:21.390 --> 00:22:22.750 quite a bit today. 00:22:22.990 --> 00:22:25.070 Now I have nuked my 00:22:25.630 --> 00:22:26.350 particular 00:22:27.945 --> 00:22:29.625 claud dot m d file. 00:22:29.705 --> 00:22:32.665 And as you can see here, there's actually an update ready. 00:22:32.825 --> 00:22:40.265 So I'm gonna go ahead and restart claud. That was weird. I actually got a weird error here at first, which I've never got before, so that was kinda interesting. 00:22:40.345 --> 00:22:41.305 Regardless, 00:22:41.305 --> 00:22:42.345 I am 00:22:42.720 --> 00:22:45.360 in Clog. The first thing that you see when you come in 00:22:45.760 --> 00:22:46.560 is 00:22:46.720 --> 00:22:48.160 this what's new. 00:22:48.640 --> 00:22:52.480 It's such a such a nice little touch. I know it's not much, 00:22:52.960 --> 00:22:53.760 um, 00:22:53.760 --> 00:22:57.520 but you've got this Clog code can now be used with Clog Pro subscriptions. 00:22:57.985 --> 00:22:59.985 You also have this upgrade, 00:23:00.305 --> 00:23:00.705 which 00:23:01.265 --> 00:23:05.585 is pretty dang sweet. That is a cool feature that they've added, 00:23:05.745 --> 00:23:09.425 uh, where before I logged out, I had to log back in to kinda link my max plan. 00:23:10.620 --> 00:23:15.020 And I can tell you right now the to do list stuff has actually been 00:23:15.260 --> 00:23:21.500 handled very well after compaction. I their compaction feature is state of the art. Like, it's incredible. 00:23:21.820 --> 00:23:30.895 So now let's just run a net here, and I'll kinda show you what this looks like and kinda talk through what it's doing. Now this actually may take a while, and I may have to speed up 00:23:32.095 --> 00:23:32.975 some of this. 00:23:33.295 --> 00:23:41.370 It's looking at the entire code base structure. It's reading some lines of code. You could see sort of the style that it adds. Like, 00:23:41.690 --> 00:23:43.610 we've got this actualizing. 00:23:43.610 --> 00:23:45.690 It keeps track of the number of tokens. 00:23:46.170 --> 00:23:53.610 There it's really informative that things are happening. This usually takes a few minutes. So what I'm gonna do here is I'm just going to 00:23:54.455 --> 00:24:02.455 periodically talk about what's happening, but mostly skip over a lot of this. So now we're at the point where it has done the analysis of my code base, 00:24:02.855 --> 00:24:11.290 and I'm gonna go ahead and say, yes. You can create that file. You can kinda see what it asks you. The second option is yes, and don't ask me again during this session. 00:24:11.610 --> 00:24:14.010 That's also a really nice thing because 00:24:14.330 --> 00:24:17.930 there are some commands when I'm working with it that I always want to approve. 00:24:18.555 --> 00:24:24.635 There are other commands that I never want to auto run, so I I like having that that control there. 00:24:24.955 --> 00:24:28.715 And you can see here that it did 15 tool users, 61,300 00:24:28.715 --> 00:24:29.595 tokens, 00:24:29.595 --> 00:24:36.910 one minute thirty six seconds, and it completed the claw dot m d file. And just to show you what that looks like here 00:24:38.190 --> 00:24:40.590 and how it actually comes together, 00:24:40.910 --> 00:24:44.350 uh, this is what it does. It kinda builds its own guide 00:24:45.385 --> 00:24:49.625 that it uses to help better, uh, kind of understand 00:24:49.625 --> 00:24:50.345 the 00:24:50.505 --> 00:24:53.305 structure of my code base. It even picked up my 00:24:53.705 --> 00:25:00.745 old folder that I'm trying to phase out of that. It's kinda migrated up into a new version of, uh, Vue. 00:25:01.600 --> 00:25:09.520 It's got all the technology that it's used. We've got all the domain models. Does a really good job with local development. Like, all of this is 100% 00:25:09.520 --> 00:25:10.240 correct. 00:25:10.640 --> 00:25:12.160 All of this is correct. 00:25:12.880 --> 00:25:14.800 So it's it's really 00:25:15.225 --> 00:25:21.945 it's really useful. And I found that this kind just having this kinda does speed up the development efforts a bit. 00:25:22.505 --> 00:25:25.225 In particular, for me, we care a lot about our design 00:25:25.545 --> 00:25:30.425 stuff. So having this in here is actually really nice as well because 00:25:30.690 --> 00:25:34.610 it doesn't need to go look in other code to try to figure out that design. 00:25:35.170 --> 00:25:45.090 You can see our integrations that it's using, so on. Right? So now I am in the RU code repos. This a public code base that you can pull down from GitHub. 00:25:45.655 --> 00:25:48.695 And I basically asked it to diagram out 00:25:49.175 --> 00:25:50.615 how the Orchestrator 00:25:50.615 --> 00:25:51.495 subtask 00:25:51.495 --> 00:25:53.095 version system works. 00:25:53.575 --> 00:25:57.255 So you can see here that it actually generates some mermaid diagram sequences. 00:25:57.680 --> 00:26:01.840 We need to load those into mermaid renderer to kinda see how that actually works. 00:26:02.160 --> 00:26:06.640 But let's not focus on that right now. Let me focus on the flow that this actually went through here. 00:26:07.440 --> 00:26:10.160 So the first thing that I ended up doing here 00:26:10.855 --> 00:26:15.575 is I basically asked it to tell me about this code base. So this is one of those generic 00:26:15.575 --> 00:26:17.415 queries that I was talking about. 00:26:18.135 --> 00:26:21.495 It read the read me. It read the package dot JSON, 00:26:21.975 --> 00:26:24.375 and it got enough information from that 00:26:24.650 --> 00:26:35.850 to give me a definition of what the code base is. It even picked up the the main components on it. This was relatively fast. Let me see if it actually tells me the time there. I don't think it does when we're this part in. Now, 00:26:36.650 --> 00:26:44.205 basically, what I I did is I ran a net on it. So let me show you what the, uh, cloud dot m d file looks like here. 00:26:44.445 --> 00:26:51.725 And you could see that it actually did 26 tool users, 90.6 k token, and ran for two and a half minutes to generate that. 00:26:52.620 --> 00:26:56.220 And I knew a good amount about the root code code base, 00:26:56.540 --> 00:27:08.365 enough to say that the majority of this I can confirm is correct, but I I'm not as familiar with every part of it. So I don't have the same ability that I do with my own code base to be able to say, yeah, that's 100% 00:27:08.365 --> 00:27:09.405 all correct. 00:27:09.965 --> 00:27:14.125 But it did generate a 149 lines of information 00:27:14.125 --> 00:27:17.885 here based on, you know, 90,000 tokens that it ran through. 00:27:18.510 --> 00:27:20.990 And you can kinda see some of the summarization there. 00:27:21.230 --> 00:27:26.430 Then I basically ask it about diagramming it out. I actually told it to ultra think through this, 00:27:27.230 --> 00:27:28.590 and you can see 00:27:29.070 --> 00:27:35.345 very particular. Like, you can feel the difference that it needs to go through. Like, look. It triggers this thinking 00:27:35.665 --> 00:27:36.865 portion in here. 00:27:37.425 --> 00:27:42.225 So you can start seeing thinking where if you go up through these, because I didn't tell it to ultrathink, 00:27:42.225 --> 00:27:45.105 you're not actually getting the thinking as part of the output here. 00:27:45.800 --> 00:27:50.840 So you could see that just carry through through all of this. Now it does slow down 00:27:51.320 --> 00:27:55.320 the process, but sometimes you really do want it to take its time 00:27:55.880 --> 00:27:57.160 and generate, 00:27:57.240 --> 00:27:59.160 you know, a more thoughtful response. 00:28:00.035 --> 00:28:04.435 Four minutes and, uh, nine seconds. So there we go. 32 tool uses, 00:28:04.515 --> 00:28:13.235 88,000 tokens, four minutes and nine seconds. So now that I've had that got sort of this high level understanding of the Orchestrator subtask system, 00:28:13.475 --> 00:28:14.835 what I would typically do now 00:28:15.660 --> 00:28:19.260 is this is a this is a feature I've been wanting in RootCode for a while, 00:28:19.740 --> 00:28:23.980 where I want to be able to represent in Root in RootCode, 00:28:24.620 --> 00:28:25.420 basically, 00:28:25.420 --> 00:28:26.700 the orchestrator 00:28:26.780 --> 00:28:28.060 and all the subtask, 00:28:28.535 --> 00:28:35.255 how much each of those you use, how much do they cost, how many tokens they use, and be able to visualize that and ideally click through them. 00:28:35.495 --> 00:28:45.690 I don't actually have an idea for I haven't set that. I figured out the design on that. But, basically, I could go and kick this off now and say, hey. Now that you have that, go figure out a way to do that 00:28:46.170 --> 00:28:52.570 and get some ideas on it. Most likely, it's not gonna be something that, um, we're going to to actually be able to keep, 00:28:52.970 --> 00:29:00.065 but that's just an idea of kinda how you can work through this. So here, you can see that it actually created its own to do list, 00:29:00.705 --> 00:29:09.025 and it's gonna work through it one by one. So if you watch my previous video where what I talked about a lot here so let me move my video over a little bit, 00:29:09.345 --> 00:29:11.665 is basically the rankings of each agent. 00:29:12.560 --> 00:29:18.560 And Cloud four does really good. Cloud four Sonnet, very specifically Sonnet, 00:29:18.720 --> 00:29:21.040 does really good in Cloud Code. 00:29:21.440 --> 00:29:26.400 And it should because it is their tool that they're building. They understand the inner working of it very well. 00:29:27.275 --> 00:29:29.515 And it kind of goes to 00:29:30.075 --> 00:29:34.875 say, like, my personal ranking is this, and I don't see this changing 00:29:35.595 --> 00:29:38.235 drastically over the next month. It has 00:29:38.475 --> 00:29:40.795 historically changed a lot. Like, one time, 00:29:41.550 --> 00:29:44.030 I was using cursor 100% of the time, 00:29:44.350 --> 00:29:48.110 and then I was using, uh, I used Klein for quite a while, 00:29:48.430 --> 00:29:54.670 and then I used Augment for quite a while. And I still use Augment now. I think they're phenomenal for certain things. 00:29:55.070 --> 00:29:56.030 And that it just 00:29:56.595 --> 00:29:59.875 you know, you kind of have felt so much sort of 00:30:00.275 --> 00:30:03.795 turbulence in this space because people are leapfrogging each other. 00:30:04.515 --> 00:30:18.380 But I think Clog Code is just this really sweet spot for me. Just it's my workhorse. So I think Cloudcode is just a sweet spot for me. I'm gonna be paying for the foreseeable future, the $100 a month until that ends up being, like I if if they start nerfing it, 00:30:19.260 --> 00:30:23.260 I'm gonna, uh, probably upgrade to the $200 a month plan. 00:30:23.835 --> 00:30:27.435 But I I really do need to try to get my spin down. So 00:30:27.835 --> 00:30:31.115 my current stack that I'm gonna be running is going to be 00:30:31.755 --> 00:30:35.835 $30 a month for AugmentCode because I'm on the grandfathered 00:30:35.835 --> 00:30:36.475 plan. 00:30:37.630 --> 00:30:40.990 I'm go I currently have $200 a month for 00:30:42.110 --> 00:30:43.230 OpenAI 00:30:44.190 --> 00:30:45.870 because of codec. 00:30:46.190 --> 00:31:03.095 There's something really special about codec being able to be on a bike ride, get something popped into your head, pull over, get kick something off, bring it back, and work on it in Clog code. Now I think there is probably a way that I could probably downgrade this now that they've given you access on, I think, the pro plan. 00:31:03.495 --> 00:31:15.220 So I'm gonna look into that because I don't know what the limits are on that. But if the limits are where I can run five, six tasks a day on Pro Plan, there's no reason for me to be on the $200 a month plan there. 00:31:16.020 --> 00:31:18.580 And then the other thing would be, like, API cost. 00:31:18.900 --> 00:31:25.935 Now my API costs are kind of crazy because eval, typically, they've started to creep up in in pricing. 00:31:26.175 --> 00:31:28.815 So, you know, I'll spend, you know, $200 00:31:28.815 --> 00:31:30.735 at eval run easy, 00:31:31.135 --> 00:31:41.520 and that's me trying to use models that are built into these systems as well. So this can actually run 200,000 200 to $1,000 a month just on trying to run, um, 00:31:41.600 --> 00:31:46.160 evals and testing all the different models and stuff. So this is for clogged code. 00:31:46.480 --> 00:31:52.405 I'm going to be having my $30 augment code. I'm gonna be keeping codecs for foreseeable future. 00:31:52.805 --> 00:31:55.765 And then this is going to be a combination of root code 00:31:56.565 --> 00:32:03.685 and any other API costs that I have. Of course, there's just going to be miscellaneous costs with with testing other things. 00:32:04.860 --> 00:32:07.340 So one thing that I'll just note in here is Google 00:32:07.420 --> 00:32:09.900 has kind of fallen way off. 00:32:10.460 --> 00:32:14.940 There is always a chance. There's some upcoming rumors about them launching something 00:32:15.340 --> 00:32:18.460 that may bring me back into using 00:32:18.885 --> 00:32:19.765 Gemini 00:32:19.765 --> 00:32:21.845 or, uh, Google models again. 00:32:22.485 --> 00:32:25.765 But it's going to it's going to be need to be, like, something 00:32:26.085 --> 00:32:28.885 pretty massively good because Cloud Code right now 00:32:29.445 --> 00:32:31.365 is in an incredible spot. 00:32:31.850 --> 00:32:46.090 Now I think that's gonna about wrap it up. There's so much I could talk about about ClockCode. Is there anything you want me to go deeper into on ClockCode? Let me know. I've been getting so much feedback on all the stuff that I've been doing. Trying my best to take that in and just continue doing better and better. 00:32:46.985 --> 00:32:47.785 Anyway, 00:32:48.025 --> 00:32:55.785 I appreciate all of you. Let me know your thoughts below. If you've had a chance to try Clogcode, if you're paying for the 100 or $200 a month plan, 00:32:55.945 --> 00:33:05.140 if you hit limits because I've never hit a limit on the $200 a month plan, but I've heard people hitting it on the $100 a month plan. So I'm curious what is gonna happen as I switch to that. 00:33:05.700 --> 00:33:09.940 Anyway, till next time, everyone. Have a wonderful, wonderful day. Peace out.