Agentic coding puts a kind of stress on GPU clusters that providers are struggling to handle. SemiAn

Can you tell me about coming up to speed on using clusters and the relationship that you have with agentic coding at this point? Because what we've heard from providers is that agentic coding has been like very difficult for them to contend with. It's not a free lunch where you, everything just works out of the box and the model can solve everything, though it can be quite helpful for debugging. I guess high-level lead-in for you is that agentic coding is like resulting in a different type of stress on the system because you can just like have these coding models get away from you in terms of what they're launching on these clusters? Do you have some of that experience that you can share?

It's very interesting because a lot of our ClusterMax testing, we lead with our CLI, CMax CLI. Please check it out. It's open source. Feel free to try it out on your managed cluster, play around with it. Check if you want to contribute, feel free to contribute. Make sure to read it before contributing. But of course, of course we do test our, we do use agent decoding for testing all these clusters. And the workload is very different. The workload is very stressful on these systems, you know? So that's why, like, we, we have cMax CLI as a front, you can say like a front end, and like the agent is just like a wrapper around it. So if there are, if there are any issues which cMax CLI faces, the agent in turn, like, debugs into it and understands what's going on.

But yeah, that's like the main use of agent decoding, even in like day-to-day, like, my work.