No need to share the full link. But if you did, your chats would remain unlisted with restricted access based on the visibility selection you choose. By default, it’s “only people with access”, but you can make it available to your whole team (on a team plan), unlisted but accessible to anyone with the link, or publicly available to everyone.
You can see that in action by trying to visit this example chat v0.app/chat/rewrite-config-issue-mFeMsLueS9C or by trying to visit your own chat in an incognito/private window where you’re not signed in to v0.
I couldn’t disagree more.
This is a huge downgrade, the product doesn’t make it easy to share, and so I’m not going to go and chop apart hundreds of examples. But everyday, there are issues that just can’t get out of. The previous models I could specify a component to change and it would change it - now I specify a component to change it reads my whole app. I tell it only to change this function in this file and it suddenly starts reviewing my whole code again. No matter what I say the agent seems to go off on tangents, spontaneously changing things I have specifically said not to change.
What is surprising is that this is the same complaint that many users shared with competitors, and yet V0 decided to introduce the Agent while removing the option to select models. Agents aren’t really good yet, so make them default but let me keep the option to select the model that I’d like to use. Why force me to have a worse experience when you had a better one. Especially, since there is very little product logic behind in terms of user experience, it is probably pricing optimization.
Absolutely - and I think it’s a bit of a byproduct of short term product metrics. Like you say it’s got to be pricing and cost, but just charge more for other model if you need to - this kind of lack of transparency and forcing a worse experience may even lead to better roi initially, but will only lose revenue long term as users move away.