Transcription
Most teams use AI tools for coding. That's just the tip of the iceberg. There's actually more to it than that. You can actually use AI tools to automate research, content creation, and even team communications with it. This one setup that I'm going to show you helps turn open code into your team's productivity engine or your personal assistant. 90% of people don't even know you can do this. If you're using open code just for code, you're missing out on hours saved every week.
Let me show you what you could be doing. If you're looking to use tools like this for your own team and you would like to have strategies implemented, hit the link down below and book a call with me and we can talk more about it. Anyway, jumping open repo here and you can see there's one file. I actually want to show you how easy it is to make this whole setup just using one file with instructions, using open code itself. You can do this with code code too if you wish. But essentially the instructions are going to build a planning and research and content creation workflow using different agents and slash commands. And that's pretty much it. I'll learn in more detail about what this actual text comes when we're running it. But to get started we're just really just going to run open code. And in open code we're literally just going to reference this stuff that we have here to build our whole thing. So, Alright, so we're literally just going to say "hey, please build our personal workflows using the file we just stated here". And we should start seeing it build our dot open code folder with all the settings in it. So we can see here it's kind of getting all this context that I built, how it's establishing this.
While we're waiting for that to build, I just want to quickly touch on some of the thoughts behind the instructions here. And it's around these three things, slash command, context, files and agents. So, I don't know about cloud code, but I know a lot about open code. Open code with slash commands, I know anything with the "at" symbol, if I refer to an external file, it's pulled in automatically as context. And that's great. That's a great way of like, you can pull a slash command to do a task. And there's always going to be reference files that you always want in. And you can manage those reference files using the "at" symbol, so it helps separate concerns. And I know it's going to be pulled into the slash command. So the slash command is like your initial prompt with context that you can pull straight in. And this is the kind of theories I'm kind of giving this, so I can then incrementally change how it behaves very systematically, which is great. And so if you do the "at" symbol and agents, just note, the agent has the option to pull it in. It still has to do a call call to bring it in in open code. And I just felt like sometimes agents don't always do that. So that's why I really prefer the slash command to bring in, you know, initial context that we really care about. And that's the main theory about these three going on here.
So one this video that I haven't touched before is we're going to install an "mcp", a local "mcp" for this project. And we're going to be using the brave "mcp". And just to go into what that looks like is if we go to the open code documentation, we just go to the "mcp" here. We can see this is pretty much how an "mcp" is configured here. I'm literally just going to copy this and go back to my code. And you kind of want it in the main folder here. So you just want this to be open code.json. And we're literally just going to paste that in. I'm going to get rid of this. All right. And now we've got our general "mcp" server here. And I'm going to go to the web again. We go to the brave "mcp" documentation. All right. So I'm going to be using this brave search API. And this is the "mcp" instructions here to install. It looks a bit different. You can't just copy and paste this, but I'm just going to copy this and then input the commands this side. So I'm just going to just do this for now and I will fix it afterwards. So we got the "mcp". We want the brave search. Yeah, that's correct. So we're literally just going to change the name here. And the type is local because we are installing it. And the one is "mpx", not "bun". We want it y. And we've got this is like the install package. We just put that in. Cool. There we go. "Enable guest environment". We want it brave API. So if we're going to do that and we'll put the API key there. All right. Now let me get rid of this. This is no longer needed to win a comment. All right.
So we're going to go get the API key for this. We're going to go to brave website. So this is the website here called brave.com. You can sign up for a free API. you can pay $0 per month, get one query per second, up to 2,000 queries per month. One thing to note, you do need to put your card in for this, even though it's free. I know, but that's what it is just sign up. And once you've signed All right. So once you land on Brave and you signed up your account, you kind of want to go to subscriptions here. So click on subscriptions. Make sure you click the subscribe button for the free account. It will ask for your card details. That's just, I think, how they want to stop abuse. So you can add your card details, and then after that, once you've subscribed, it will charge you nothing. Don't worry. You can then press on API keys. When you go to API keys, you'll see pretty much nothing here, but you can go to the top here and add your own API key. And then from this, you can copy whatever the API key is and go back to your code and paste it in here.
So we back after jumping around, doing the Brave thing, and we can see our agent has built everything. So let's have a quick look. So we can see at the top here, it made the open code folder. It used, it made some agents, command and context, and then it's made some just normal files where we'll store all of this. Let's have a quick look. So in agent strategy, we can come here and just have a quick look to make sure this is correct. This is a subagent. I don't think that is correct. I kind of want this to be a primary agent. I'm going to change that. And we can see it creates all the things. Great. So it knows how it needs to write everything. Not too bad. And you got my life strategy agent. Great. And then we've got our research. Is this also a primary? That's primary. And this is a sub. A research agent as a sub. I think that's fine. We don't always need to use a research agent as a primary one. We can change that if we need be. All right. But we can see it pretty much has everything in it, which is awesome. can go to our slash commands because this is pretty much what we really care about. So we're going to plan a blog post. We can just run a blog post here. The same with the daily plan. Prioritize plan for the daily. And we can do research, Twitter thread. And we got a context of what the blog pattern should look like. But our brand voice. We've got our Twitter patterns. Awesome. And we've got essential patterns also. All put it here. And we've got some life goals and routines. We can come in and update all this. But right.
So one thing to note, we've made this with open code. We actually have to exit the session because what everything we've just created here, both with the MCP and all the agents aren't in the session yet. We actually have to open it. Sorry. Close it and reopen it. So I'm just going to reopen it and we get open code starting again. And to see that it's working, we can press tab to see if the agents change and we can see content strategy agents is there, which is awesome. So I'm going to use this as an example and I'm going to ask it to create a got the blog post slack in there, which is great. And I'm going to do a topic So I'm just going to ask you to make a blog post. I want to make sure you know what a tooling is picking up in straightforward. And what we should see happen is it should reference the research agent. I don't actually hold on. I didn't know if it has that. All right. I saw one mistake before carrying on in my content agent here. I actually see no reference to the research agent, which is kind of core for what I care about. I'm just literally going to come in here and say always use the research agent to gather information and for if a URL is provided. And I'm just going to press an at here so it knows it's the research agent. And it should then make sure resource assistant agent. That's correct. So now it shouldn't use. now it should just use this research agent constantly. I'm just going to exit open code again and start want to build a blog post again. So I'm going to just ask to make a blog post about why AIT leading is so popular in 25 and the process costs. And what we'll see it should hopefully give some the agent and go from there. So we can see here it is saying let me gather some research insights and we can see it's delegating, which is kind of what we want. And there we go. We are asking the research agent. Remember the brave API only allows us to do one search per second. Sometimes that may be an issue. And we might actually have to prompt that say, hey, when you do a search, wait one section before you do another one. And that's something to note. But we can see here it is doing quite a bit of research here. It's grabbing a few different queries can go right left to see what's going on in it. So we can see, nope, no, no issues. It actually is giving us the response back, which is great. No issues so far. All right. And we can see what it's looking at. Mackenzie really trying to grab all the different bits of research here. We could actually do a better prompt on how research should be structured and altered through. But for this demo purposes, I'm just showing you a quick way of doing it. All right. So once it's done its research, it'll come back It's making a folder and then it will save it. right, so it is done running. So we can see, if we just quickly scroll up. You can see here it did the research. Then it actually made a file where we're going to put this. And it actually went and grabbed the brand voice from what we wanted. And it actually then built a whole blog post and then saved it. We can see our new blog post that's there. And this is just a draft. You probably want to come here and edit it and change it how you want it to be.
last one I just want to show off is, so this is do slash new because we don't want this context. probably build our life, daily plan. So we can just go daily plan. so we just use the slash plan. And we're just going to ask you to help us build each of those up. We'll see how it does. So we're just running that and it's just analyzing the request. I'm actually realizing I ran the wrong agent. hey, we're going to just build up our life planner quickly. And at the moment, you can see I'm still in the content strategy agent. I'm just going to press tab here to go to the life strategy agent, just so we're using the right agent here for the job that we specified here, but it knows how everything works. And I'm then going to just use the daily plan slash command. So it just grabs all the different contexts. All right, so I'm just going to go slash daily plan, and then I'm going to give it what I'm trying to do here. And my focuses are just fixing code and content generation. And I'm just going to produce enter, and that's literally going to start building up my plans for everything. It should also make some templates that will help us on track. (Audio Out) All right, so this is hosting for our confirmation. And yep, I think this sounds good. All right, we can see it's really going to a lot of different detail here. Probably maybe too much, but it's really nice to see how much you can just build with this very quickly. All right, we can see on the screen it is finished with our daily update, and we can start today. We can just run our daily startup, and we can do September the 12th. So let's do that. I'm literally just going to run this, grab that, and let's see what happens. All right, so we can see it's telling me where to focus on, and how to really block everything, very standard stuff. We could just refine this to do a lot more, especially like maybe journaling what I did, what I did well, and then also making sure that it's getting the metrics done for me.
we showed how we can use AI tooling, not just for coding, but actually for personal productivity or just for individual productivity. You can actually use this in teams and really accelerate your team's productivity and communication, a lot more than it could before. You can get consistency across teams' outputs, reduce context switching, faster stakeholder communication. Imagine every time you commit code, a message goes out to your Slack channel that, hey, this code has been committed, and this is what I worked on, automatically giving all the relevant information, that you didn't have to manually type yourself. This is a streamlined development workflow. covered how you can do this, but the way you should always start is, we start small, pick one non-coding workflow, like research or documentation to get started, and then measure the impact. Does it actually save you time? Is it actually giving you better results, or is it actually taking time away from you? It's not just the usage. This is very important. A lot of people get caught up, me included, it's the hype, it's what we should be doing, but the results don't match what we expect. That's fine. You can dial it back, maybe try a different approach. Really approach this in a systematic way. Once you've measured the impact and you know it's saving you time, then you're doing a great job, not just using it. Then the next step is you want to scale gradually. You can add different MCPs for maybe accessing different contexts or sending out different requests or alerts, and that's great. But always make sure it's valuable. Don't just add it for the sake of adding complexity. Engineers, we love to do this, back and really make sure it works. And lastly, if you are putting this in a team setting, show them the reasons why it works and why to use the automation, not just, "Hey, this is the automation, do this." Explain the reasons why. Then once you've got the reasons why, go into the details of how best to use it and roll it out slowly. Don't try, do it all at once. That would be my recommendation here.
so that's how smart people and smart teams are actually using AI tooling like Open Code here, not just for coding but also for workflow, for transformations. Most development teams are sitting on this goldmine and not even realizing it. So if you're a CTO or a team lead wondering how AI tools like this can fit into your strategy, help teams navigate these exact decisions. So I've got a link down below if you want to book a free consultation for 15 minutes, we can talk to you if it is even needed or how you could approach this in your own team. what non-coding workflows would you like to use to save you time? hear in the comments down below. always, if there's anything you ask you want me to cover, please drop me a comment and I'll happily engage you there. And thanks so much for watching and I'll see you next time. Cheers. (Typing)