Live demo: MCP connection overhead multiplies with sub-agents

dedicated stateful connections bound between it and external services. I'm going to show you one of the silliest examples of how this affects you in day-to-day. I'm going to spin up codeex. It's trying to failing to initialize the Xcode build MCP. So I got an error there. But watch what happens when I say sup. I'm hitting enter now. Oh, did they suppress it finally? They suppressed it finally. Cool. I gave them a shitload of feedback about this. There was a problem where every time you spun up a thread in codeex, it would block your first message until it finished initializing the MCP servers for computer use and whatnot. They recently changed it so that those wouldn't happen until after you send, which helped a bit, but they have changed it even further where you don't see it as much now, which is good. But previously it was obnoxious because every thread and more importantly every sub aent would have to spin up five or more stateful MCP connections which means that on your computer if you have one agent run you're doing in codecs and it spins up five sub aents that is now 30 stateful connections that are bound on your machine for one prompt and that is for the server and the client because it has to spin up the server side for that locally for all the computer use servers in case any one of those sub aents wants to do computer use and now you have 30 stateful processes on the server side in codecs and then they're bound 30 times on the client. It is so much overhead and if you have seen CIS policyd