> If you have suggestions on how to name our products better, I'm all ears. Our intention is to make things clear and simple, even if we miss the mark sometimes.

I'm not the one you were talking with but catching you is godsend since I just ran into a lot of confusion on the naming myself. I think some of it has to do with how they are labeled in the app.

I think simple numbers in naming is great, even 6.1 is fine bc I understand that if I want the latest model, I just need to look for the biggest number. Where I got confused is in the "work" tab, I saw 'Astra' is set as the default. I see the label for it is:

"Frontier intelligence for your most demanding tasks."

To me that reads "this is the 'best' model." Then I see Sol-6.1 which is labeled:

"For coding and every day work."

Then Terra-6.1 is:

"Terra 6.1 Codex Model" (tbh this one might be the most confusing, I'm aware of codex the product but Sol is the one labeled good at coding)

From my POV as a basic plan-based user wanting to do something like...

> design a robust event-driven system, here's the details [...]

I honestly have no idea which one I should use.

Would Astra-6 produce a better design than Sol-6.1? Is the '.1' a big step up from Sol-6? (I'm guessing no but I truly have no idea). I would assume the answer is Astra-6 would produce the best one, even though the labels don't imply it is necessarily geared towards coding?

But tbh the "default" seems to always work for me... and after reading your comment, typing this one out, being forced to think about it... it doesn't seem too bad given your challenges in communicating the purposes of each model and wide audience of consumers. I'm also sure anyone could find a million problems with decisions I've made in software I've built so I try to not be too harsh :)