Claude Code NEW Sub Agents in 7 Minutes

Anthropic has just released sub agents for cloud code. What the feature allows you to do is essentially create your own team of specialized AI agents for different aspects of your development workflow. You can equip each agent that operates independently with its own context and expertise as well as their respective MCP tools or system prompt. This lets you delegate specific workflows like code reviews, debugging or testing to dedicated AI specialists that you defined while keeping the conversation focused on the big picture. Now, in this video, I'm going to show you how you can set up sub agents as well as how you can think about potentially leveraging within building out your application. Let's dive in. Once you're within Cloud Code, all that you need to do to create new agents is you can forward slash agents. Once you're within there, you can create a new agent. You can specify whether the agent is going to live within the project or whether it's going to be globally on your machine where you can access it within any project. And then from there you can either manually configure or generate with claude the agent that you want to create. In this case I'm going to say I want to create a front-end engineer that is an expert in nex.js tailwind as well as shadui. What it's going to do is it's going to generate a markdown file that we can go and we can iterate on as we build out that agent. And the really great thing with this is we can specify which tools that we want to give the agent access to. We have all of the core cloud code functions like being able to list out the different files within a directory, read or edit files, all of the different features that you're probably familiar with. Additionally, if you do have any MCP servers, we are going to be able to leverage those within the agent. And within here, you can go and turn on or off all of the different whether it's MCP tools or the core functionality that you want to give the agent access to. Now, for this particular agent, I'm going to give it access to everything. Where this is helpful is you can specify to have a backend agent that might have access to read your database and run SQL commands and potentially read the logs of your infrastructure or whatever it might be. Whereas on the front end, maybe it has access to a whole host of different tools. And additionally, what you can do is let's say you're using a brand new front-end framework or something and the documentation isn't in the training data of the LLM.