You can rename the chat instantly though still, right? Just wanting to make sure that is still working. But also to better understand, you want to fork the chat but keep it the same name as the original chat? Also you can organise chats into both folders and / or projects still just as simple as prior. If the chat was started in a project, it will also stay in that project. Please send screenshots if possible for a better view of what is happening.

The chats are thematically like branches, where each one corresponds to a feature/task that's being worked on. I agree it's hard to tell from the sidebar which project each branch belongs to, I'll pass it along to the design team to see what we can do

On new chat creation, no, that’s removed now. It’s just “Duplicate”. Renaming can only be done manually now. But if you rename before message 1, the system still overwrites it. So basically just turn off the message 1 overwrite, that’s the main gripe. Because on new chat creation now, it sill properly just adds the (1) or (2) to the name of the old chat. This is good. But then it overwrites the whole name after message 1.

It may sound nitpicky, but for context I’m averaging about 10 messages per chat on the mini model before it starts to go squirrely. So I could rack up 15 chats in a day, across multiple projects. So this is actually super annoying. I don’t have time to manually change names on every chat.

A screenshot below of multiple projects on the new version. I have no idea of knowing which project these chats apply to. (There’s 2 different projects in that list).

.

.

Old version here:

See how much easier the old one is? At least I know which project they apply to. Again, if the auto-rename just replaced the (2) (3) (4) etc, that’s perfectly fine and helpful. IE: “Canadian Arctic Planner - Tooltip Title Changes”. Great! But keeping the original project/chat name is critical for me.

Ah ok I see now. And agree with what you are saying. I am wondering, if you are using these various chats as feature branches maybe, what if you just used github integration and worked that way? Less chats but all same project still.

But as you saw Jacob has pushed this to the team so it will be looked at further. Hope there is a solution soon which works of course. Keep us updated if you feel it is being resolved.

Shared with the team! I agree, it would be easier to manage

Thanks again for the feedback!

Thanks as always @pawlean

@heystu I fork the chat to clear context window. After like 10-15 messages the Mini Model goes squirrely and cost increases quite a bit. It’s just context management and extremely heavy babysitting of the model.

While I could use Claude or Max models and have bigger context, costs just go way too high, and they compound with added context of longer chats. Mini does most of what I need so I just mini-batch the dev and progress function-by-function after the main app layout is established. I use new chats for each function (ish), or when I hit 10-15 messages and the model goes wonky. Sometimes I have multiple chats per function if it struggles.

On a cost basis I’m probably saving 98% vs Claude or Max in a 40-60 message context window via this method with Mini. I’m sure Vercel doesn’t like that, but hey, thems the breaks.

A full scale app could be 1,000 to 1,500 messages, or more. Depends. If we could clear context another way, that would be another method to reduce the number of chats, but ya. I don’t use GitHub, all local on Vercel for now. Thanks again man!

Hey! To help debug your v0 project, could you share your v0 chat link? It looks like https://v0.app/chat/... — you can copy it from your browser's address bar while in the chat.

You'll also need to unlist the chat so our team can view it — here's how: https://v0.app/docs/sharing

v0.app

Sharing | v0 Docs

Share your v0 chat with others to showcase your prompt history or to collaborate on generating components. This allows for seamless teamwork and feedback.

This helps the team reproduce what you're seeing much faster. Thanks!

Bot, you don’t need a chat link. Fork a new chat, after the first message the system auto-renames. It’s app-wide on all instances.

Can we please get this fixed/disabled? Using V0 is like Chinese water torture here lately. There are too many bugs making it almost unusable since the January horror-show update…..

I’m wondering if the fix will extend to projects? I’ve just created a new project from a duplicated chat after making some edits in draft mode. I didn’t notice that the project name had been changed and that got built into the url. I’ve been able to change the domain name (I think), but I can’t figure out how to change the project name.