Assistant is referred to as a "private" or "closed" beta, when it is not.

Zambyte

Apologies if this is not the best way to report this. This is a recurring documentation issue; I suspect due to a misunderstanding of what a "private" beta is. Here is what GPT 4 Turbo has to say about the difference between private and public beta software:

A private beta is a testing phase where a limited number of users are invited to try out the software, often with the intention of finding bugs and providing feedback in a controlled environment. Access is restricted, and participants are usually selected based on certain criteria or through direct invitation.

A public beta, on the other hand, is open to anyone interested. It allows for a broader range of feedback and testing across various user environments, but it can also lead to a higher volume of feedback, which can be more challenging to manage. Public betas are often used as a marketing tool as well as a testing method.

The Assistant feature is referred to as a "private" beta on the stats page, and as a "closed" beta in the documentation. Since anyone interested can pay for access, this is not accurate.

Simply saying that the Assistant is in "beta" would be the best I think.

Vlad

Zambyte I do not see anything wrong with the naming (it is both private and closed to me) but I invite you to edit the documentation to clarify it (it is open source) as I do not see any problems with either.

Zambyte

Vlad I made this thread instead of contributing because the stats page is not open source as far as I know. It's not a big deal, but private / closed beta and public / open beta mean specific things, and the Assistant falls squarely under the latter.

https://en.wikipedia.org/wiki/Software_release_life_cycle#Open_and_closed_beta

The difference is that if it were a closed beta, only people that you actually invite could use it. Since anyone can join without being invited, it is an open beta. This confusion might lead fewer people to try out Ultimate for access to the features. I know I was hesitant, because I wasn't sure if I would be invited.

I'll open up an MR for the documentation though.

Zambyte

https://github.com/kagisearch/kagi-docs/pull/323