with um that you built relationships with. Um and and then from a a platform perspective, you know, we support um running we support, you know, tracking the different agents that you're running. So you have this swarm of agents. Maybe you've kicked off um maybe you're kicking off a signal which which is our agent. It's running periodically. Maybe you're kicking off your you know you've named another agent um in the system. And these all support, you know, viewing the session that that ran, downloading the transcript, and you can resume a clouded session locally, too. So, the idea is that this thing's constantly running. You're picking the harness, the sandbox. You're deciding the prompt if you want, hey, don't be aggressive or look for, you know, look for security issues. So, you're deciding the prompts that drive this and you're also deciding the skills that go along with this. So um in a preset here um I can add you know add different skills. I can add my own skills. I can link repos. I can I have pre-baked skills too. Um so the ideas observability platforms are really starting to get are becoming tied to the continuous loop to the the fix not just the the signal. Um, and and you you want to take your local experience you have debugging the stuff locally. You want to take the evals that are running and and actually have these all work in something that puts up a fix or at least gets you a cold start and then I can take it over locally if I want to continue debugging uh from from here.