So, first we have sub agents. Nowadays, whatever harness you're using, you can spawn new sub agents. You can have a You can have an army of them. And get work trees are your best friend. So, think of work trees as isolated folders. And inside these folders, the agent writes whatever code it's generating. So, you want these work trees to be in parallel. So, the sub agents are doing independent tasks and are not fighting over the same thing. Second, we have skills. These are your organization secret recipes. So, make sure you have a lot of skills because these skills, once you start say giving it to your agents, the agents will always make sure to use the correct and proper workflows to solve whatever production bug you're facing. And of course, all of us have seen a lot of MCP tools being shipped into the market right now. Everybody says we can, yeah, the agent can connect to whatever MCP tool and whatever third-party server there is. And your client data can live in any system you want. And at the end of the day, if you have a lot of sub-agents, you have a lot of work to orchestrate. So, minimal UX is the key here. Let's look at the sub-agents. With you as the orchestrator, you can have, let's say, with 48 GB of RAM on your MacBook, you can have 50 active work trees. That is 50 active sub-agents working independently on different tasks. So, where do these tasks come from? So, let's say the production software you're going to ship has a lot of bugs that your QA is reporting. So, all the Jira tickets can be thought of in a separate different work tree. So, different work trees are handled by a separate agent, and these agents can spawn multiple sub-agents to solve that particular task. You don't want to queue up your tasks because the agent is will do that a lot better than you.