Yeah.

Yeah.

Yeah, for sure.

But that was the thing back then.

It's like, And it's like everybody was like, you know, hey, that's the way how we are going to connect to different tools.

And I think, I believe it still is.

But as we were starting to develop our internal processes around agents and scale our agentic use, we have realized that it's maybe it's something different and it's not one or the other thing, but it's actually both things or all things because all the developers, they have a special references and they have their good reasons why they prefer one or the other.

So what's next? What are you working on? What are the hot tips for the rest of this year?

How easy it is for them to migrate to Semaphore?

Yeah, I think before the coding agent, that was a challenge.

But one of the reasons why we are so excited about the SEM AI and its rollout is that it's not only about the core interface to the functions of Semaphore, but it is also about the whole skill set that they have developed and put into the skills.

Because we have these codecs and plot codes plugins so basically as we are developing skills they are you know getting updated for you automatically but what we try to do in these skills we have tried to kind of put in all the knowledge all our expertise cicd expertise and one of these expertise is also how to migrate from you know different cicd tools to sound so so for example like you know one key component of a semi is actually migrating from github actions to sound because the the most important thing you know is to enable people to experience it themselves.

Because you can put a lot of nice things on your website and, you know, they can be credible and you can, as we are in a fully open source company, we also talk about how do we do testing.

Like, you know, this is, you know, transparency is great.

But the most important thing for the people is that they experience, you know, themselves, you know, and then if they have a pipeline that is kind of like lasting 30 minutes, for example, on GitHub Actions, that they really experience that it is 15 minutes.

team