Sid Sijbrandij

It's not trivial to select the best model, and people also have their own preferences.

And what people especially don't want that choose Keyload, they don't want the model to switch up on them.

They don't want auto model where you don't really know what it did.

And they also want to be sure that they're using the exact same thing the whole time.

So if I say I want that, I want exact that with the exact context window because it's very frustrating if...

you're randomly using another model or somehow the context window is half of what you're used to.

Right.

I think humans are really good at kind of using, selecting the right model for the right task, but you don't want the software to change it up on them unless they give you permission and then still you want to know what exactly was used.

In Kilo, you have profiles and you kind of set your own profile.

And that's a combination of want to use this model, but I also want to include these prompts.

You can even share these profiles across your organization.

So you collectively work together of like, this is a really good agent for upgrading our Java code or something like that.

Yeah.

And you're basically creating team members and just like in a real company, like it's helpful to have the same team member.

Now, these these profiles don't have memory yet.

That's something for the future.

But they already have a collection of prompts that are super helpful for that company, for example, and simply your style guidelines or like I try to upgrade our Java before and it needed these and these prompts to be effective.

So being able to share at least these prompts is super helpful.

Yeah, so it's all the VS Code based editors, all the JetBrains editors, it's available.

There's a CLI that you can run anywhere.