I've been using Cloud Code a lot lately. It's really surpassed cursor for me for all my AI coding needs. Hey, my name is Ben. In this video, I'm going to show you the top three productivity tips that I've learned from my hundreds of hours of using cloud code. Let's go. This first tip addresses something that really can kill your flow in Cloud Code. If we do something simple in a project, especially on the first time we say start a dev server, it's going to go and it's going to ask us for permission to actually run the command or edit the code, whatever the case may be. And then it gives you three options. You can either just proceed with it. You can proceed with it and then don't ask again for that particular command. And then third, you can just say no, I don't want to do it differently. But as I was using cloud code more and more, I found myself always just picking two no matter what. I found with cloud code, it doesn't really try to do anything crazy ever. So there's not really any reason to always ask this question. I'll show you a different way to open cloud code. So you don't have to always approve all those permissions. To bypass permissions, what you have to do is launch cloud normally, but then add a flag dash dash dangerously skip permissions. And now when you open it up, we're going to see a message here saying bypassing permissions. And now if we ask to start the dev server, it's just going to do it. It's not going to ask for permission or not going to give us those options anymore. Obviously, this does introduce a bit more risk because now clock can do anything on your system. So, there are some hooks you can add in that gives you some protection. You could add in a hook that prevents it from going outside the scope of your project folder. You could also add a hook that stops it from removing files. But to be honest, I don't find those are used actually very much at all cuz like I said, claw doesn't do any crazy changes from my personal experience. Always putting in that flag every time can be a bit annoying. There's a shortcut you can use so you can create an alias on your system. That's what I did. So you can create an alias that maps the just the word claude to Claude with that dangerously skip permissions flag. So I'll put that in the description of the video if you want to use that. Once that's in place, now I can just open claude like normal. And now it's going to bypass permissions by default. So do your own research. Make sure this is a good fit for you to bypass permissions. But for me, it's giving me a productivity boost because it allows cloud code to work more in agent mode. You're in cursor and you're in your project. If you just do the init command, what it does is builds you a cla.md file. So markdown file. The unique thing about it though is that every time cla loads, it loads this cloud MD file in there. And there I created it. And this file has the essential development commands, architecture overview, and key components. That's great and it's it's useful, but this next productivity hack will make it even better. So, if we look here at what it created, it's done a really good job of creating this file, but what I find is adding a section for shortcuts really helps and really saves a lot of time. I'm going to add command shortcuts here. The ones I'm going to use for this example are around GitHub. So, creating feature branches in GitHub, doing pull requests, pushing your code to GitHub. Cloud code is a bit weak on restore points and backups. So, this actually these commands are a real lifesaver. So if you look at the first one, I just give it a short like two or three letter acronym for the command I want and then I remember all the commands because I use them all the time. So for example, NB here will be creates a new branch for feature development. So creates a feature branch. Something like PPR publishes the PR the pull request and creates good commit messages. So you can do this for whatever kind of commands you want in your application that you use all the time. It's going to save you a lot of time in cloud code. So let's look at an example. So now in cloud code I can just use those shortcuts. So now I'm going to say NB for new branch and then say what the branch is going to be about. So this is going to be create a branch to detect duplicate locations. Now it's going to know what that command means. It's going to create the branch. It's going to name it nicely for me. So say detect duplicate locations. Now the branch is all ready for me to go. And all I have to do to get this hooked up by the way is I just installed GitHub desktop linked it to my GitHub account. And that gave Cloud Code full access to my GitHub account so I can create all these feature branches etc. Now that's created, I can just do my coding as usual. I'm going to say add a warning if a location has the same address and zip code as one already in the system. The clock code will go out as normal, do its thing, but now I have that feature branch created. So I can actually just commit the changes it's doing. So now it's done coding, I can just commit those changes to that branch right inside Cloud Code. And it's really nice because it kind of makes up for some of those lacking restore point features in Cloud Code. It allows me to quickly back up files to GitHub, keep a good version track and then I'll show you in a second. It does really good documentation. We can also use our create pull request command here and that's going to go out to GitHub and again it's going to create a pull request. There is actually a GitHub app built for cloud code. So you can say install GitHub app here and that's probably the recommended way to do it. So you definitely try that out. But from my experience using the the CloudMD file and just putting in those custom commands works really well for me and it's really enhanced my productivity. And this is just one example like using GitHub, but there's I'm sure all kinds of things you can think of to add to the CloudMD file as shortcuts. And if we look at the pull request it actually created in GitHub, it did a really nice job of documenting it. It has a really nice summary, key features, even the test plan in here. And it's very useful documentation. This one thing I'm seeing in the industry right now is everyone's at least starting with using AI for documentation. It is a really good first use case and cloud code does it really well. This next productivity tip is a bit of a two for one. So, first it's about how your screen's laid out for maximum productivity. In this case, I want to see everything I can. What I suggest is you have a vertical monitor. So, you see this on the left here. This would be your code. So, your cursor or your Visual Studio Code, whatever you're using, that would be dedicated monitor that's vertical. Then, your second monitor could be more horizontal and you could have on that one, you could have cloud code in a separate terminal. You could also have the application you're building. This way you can just look at the application. It's going to do a hot refresh when you do changes and just do commands and cloud code. Everything's just right there right in front of you. And then you can see the code being updated in real time as you go. And by the way, when you do have the second monitor set up with a separate terminal window, you can actually connect it to your IDE. So you just do a / ID command and it's going to give you a list of the IDEs you have installed and you have this configured in. So now I can just say cursor and now it's linked up. So that just ties everything together between your two monitors. And now I have all my windows positioned. So everything's in front of me. So I can do rapid development using Claude Code's queuing methods. If you're used to cursor like I was, you kind of used to you put in your prompt and you wait for it to finish and then you put in your next one. But Cloud Code is actually way better for this and it's got a really powerful queuing feature. But check this out. I just put in the prompt add sort for website column. But while it's actually cooking away and doing that, if I put in another command like add icon to store locations and I hit enter. So now you see it's actually been cued here and Claude's actually going to go through all these cued messages and do them not necessarily in the order you present them, but it's going to kind of combine them and do really intelligent way of doing all the changes for you kind of together. What I find myself doing is like now that I have everything on my screen, I can see the application and see the changes coming in real time. I just keep putting in things I want changed and just not worrying about the order or anything. Just keep putting them in there, queuing them up. So, Claude Code just does it for me. And then I keep iterating in real time. Just a little bit of time while I was talking. It took those two cued messages and did both the changes. Added sorting to my website column and added this nice little icon for my store locations. So, when you're using cloud code, make sure you invest the time to get your system set up how you want it with the windows and screens all how you want it. Also, make constant use of the queueing feature is really powerful. Just blast away with all your changes and let Cloud Code manage it and do them all for you. I think we're in a period of time right now where if you really understand how to use Cloud Code effectively, you really have an unfair advantage. I'm going to do more videos on Cloud Code coming up. Everything from tips and tricks like this one to actual application builds. If that's interesting to you, make sure you subscribe to the channel. I hope you're having an amazing day. I'll talk to you in the next one.