⌘K
Pauline P. Narvas - **Folders** are now purely organizational tools to group your chats (no deployment sharing) - **Projects** are now true Vercel Projects that control deployments, domains, and environment variables - To create a folder: Go to your Library and use the folder creation option there - To move chats between projects: Click the settings icon in the chat sidebar → Reassign project - Multiple chats can still share the same Project (and thus the same deployment URL) - you just reassign them to the same Project The UI for this is definitely different from before. If you need to share deployments between chats like you used to, make sure those chats are assigned to the same Project, not just in the same folder. https://v0.app/docs/faqs#whats-the-difference-between-folders-and-projects
system 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 This helps the team reproduce what you're seeing much faster. Thanks!
Tomraab90 3126 I can’t find the Library anymore and Reassigning a project is also not visible in the UI for me
Jacob Paris If you've published it to Vercel, then you'll need to delete the project on Vercel's side as well. You can go to vercel.com and log in there and see a list of your projects
Jacob Paris @alinamartynenko-2263, just checking in to see if you still need help hiding your published prototype. Have you had a chance to look into deleting the project on Vercel? Let me know if that helps!
Pauline P. Narvas Hey, @kamalabdulmumin0-gma! Welcome to the Vercel Community 
If I'm understanding correctly, you'd want to set up something like what is detailed in this guide: https://vercel.com/guides/how-can-i-serve-multiple-projects-under-a-single-domain Let us know how you get on!
Pauline P. Narvas Hey @kamalabdulmumin0-gma, just checking in to see if you still need help with integrating your three projects or if you've made any progress. Let us know if you have any questions or need further assistance!
Jacob Paris You should be careful about all dependencies you add to your project, it doesn't matter if they come from skills.sh or npm, supply chain risks are the same But we do see the need for better solutions here and we have some on the way
Mealai Awesome! Is there an ETA? How difficult would it be to use them itmt? They have shields.io integration and api docs and they’re doing everything for free? Https://oathe.ai/docs
Jacob Paris Skills Audits has launched here now https://skills.sh/audits
Pauline P. Narvas I hear you. The recent v0 beta update replaced the "Publish" button with a GitHub-integrated workflow. Here's how to publish now: 1. Click the Git section in the sidebar to connect to GitHub 2. Create a repository if you haven't already 3. Use "Open PR" to publish via pull request Not seeing publish/PR options? Try generating new code with a prompt, duplicating your chat from settings, or clicking on a versioned message. For quality issues, the beta is still being refined. Being more specific with prompts and breaking complex requests into smaller steps can help. You can also export as .zip and reimport if a chat gets stuck. Happy to help walk you through the GitHub setup if you'd like! 🙏 Though, if you are seeing issues right now, they may be related to the git incident happening right now. These docs may help: https://v0.app/docs/quickstart https://v0.app/docs/github
Ben 9781 I am really worried - we use this daily and have multiple client projects that i fear we wont deliver based on the BETA - if we can’t OPT out of BETA can someone jump on a zoom for 20 mins to talk through as this could be business closing for us.
Alexcumbers 9492 **Subject:** Feedback on Beta Deployment Strategy and Production Stability Hi Pauline, I’m reaching out to share some critical feedback regarding the current development cycle (I assume Ary is still leading as PM?). While it’s exciting to see **v0** evolving so rapidly, the current approach of replacing stable, reliable functionality with Beta-quality features is causing significant friction. As a senior developer, I have to emphasize that forced migrations to Beta features aren't aligned with professional environment standards. A few key observations: * **Standard Practice:** Major paid services typically offer an **opt-in** for Beta testing rather than a forced rollout. * **Visibility:** Because web environments update silently, we often only discover breaking changes when workflows fail. * **Recommendation:** Could the team move significant Beta changes to a separate, **optional playground**? This allows for community Q/A without jeopardizing production-dependent projects. On a side note, I’ve noticed the **Design Preview** is currently down while waiting on fixes, and there's a bug where importing projects with a `/public` folder fails to save. I’ll report the latter formally. thanks
Jacob Paris How are you injecting the cookie? Can you add it in a request interceptor instead so it resolves at request time instead of ahead of time?
Bharathrnair7 1528 async function processQueue(newAccessToken?: string, error?: any) { while (requestQueue.length) { const queued = requestQueue.shift(); if (!queued) continue; if (error) { queued.reject(error); } else { try { // Explicitly set the new token on the queued request config // instead of relying on the interceptor (which reads stale cookies) if (newAccessToken) { queued.config.headers = { ...queued.config.headers, Authorization: \`Bearer ${newAccessToken}\`, }; } const response = await http(queued.config); queued.resolve(response); } catch (err) { queued.reject(err); } } } } try { const newAccessToken = await handleTokenRefresh(); // process all queued requests with the new token await processQueue(newAccessToken); // retry the original request with the new token explicitly originalRequest!.headers.Authorization = \`Bearer ${newAccessToken}\`; const retryResponse = await http(originalRequest!); response.data = retryResponse.data.Output; response.messages = \["Your request was processed successfully."\]; } finally { isRefreshing = false; } im injecting the cookies, in interceptor itself
Robin Mate Correct. If that is a new strategy: very bad. Combined with the changed pricing policy, even worse. Continous work seems to become impossible.
Dzhnikolova Yes, totally agree! I was forced to update and the new way of deployment is super annoying! I lost changes, have to merge new branches all the time and from an easy flow, we now moved to much more complex way of deployment. Is there a way to switch back to the previous version of deployment?
