Taylor Mullen

In a meeting, like, oh, people are reporting that something is broken.

Yeah.

Think of how many products you've used where something doesn't work as expected.

Well, we talk about it as well.

We want to fix it just as much as it sucks for that it's broken.

We also want to fix it.

So the other flow is we'll very much say, hey, can you just pull my chat with so-and-so and fix it?

And it'll just kick it off.

And we do this all the time where some folks, what they'll end up doing is they've taught their CLIs to spawn other CLIs.

And so you'll have like one kind of orchestrator which then spawns other ones.

And then so it will manage the life cycles of those.

And then before you know it, you have all these CLIs spawning CLIs and all these CLIs kind of iteratively working through the problem.

But granted, like we do this with the notion of

With great power comes great responsibility.

Yeah.

Right.

The CLS, they can do anything.

And so we have guardrails in place.

So when one of these actions occur that could be impacting in some way, it waits for the user to respond.

So you'll be told, hey, you need to go ahead and approve this action or not approve this action.