Amy Egan Thanks for the feedback! I've shared it with the team 😃

Anshuman Bhardwaj Hi @shige, thanks for taking the initiative for this with a PR. I'll share it with our team. If you are confident about the PR feel free to make it ready so maintainers can review.

Tadashi Shigeoka Thanks, @anshumanb san! I’ve marked the PR as ready for review. Looking forward to the team’s feedback.

Anshuman Bhardwaj Hi @schutzworks, welcome to the Vercel Community! Can you try setting the header value in vercel.json to an empty string? vercel.com/docs/project-configuration/vercel-json#headers

Manu Yes, this would be amazing. Right now I’m exporting JSON and letting Claude figure it out, but having them queryable directly via MCP would be amazing.

Pauline P. Narvas Thank you both for the request! We've passed it on internally and will keep this thread updated with any news.

Stefan Smiljkovic Is this ever taken care? There is another thread that is not working for Vercel MCP and I am facing it as well. community.vercel.com/t/vercel-mcp-get-runtime-logs-returns-no-logs-in-claude-code-cli/35417

Pauline P. Narvas This is a great feature request! Thank you for taking the time to share it with the community. Let me pass this onto our team internally :) I'll let you know if we have any additional comments!

Lucas Vieira Thanks for sharing the workaround. The next.config.ts file tracing approach works, but it’s undocumented and breaks whenever Next.js changes its bundling behavior (which happens more often than you’d think). For anyone reading this who doesn’t want to maintain that config, there are alternatives that avoid the Chromium binary problem entirely: Client-side: jsPDF or html2pdf.js for simple PDFs (limited CSS support, but zero server deps) gotenberg.dev — open source, self-hosted. Run Chromium in a Docker container and call it via HTTP from your serverless function. Full quality, you manage the in

Pauline P. Narvas Does this help? help.flexclip.com/en/articles/11520991-what-to-do-if-google-chrome-crashes-and-pops-up-an-out-of-memory-error-message

AbbielG2 Yeah helps a bit but still crashes, i thing it’s because i use large images on the page im trying to preview. When the images load, site gets stuck than crashes :(

system Hi @community-backoffice! Thanks for posting. I'm here to help! If you'd like to speak with a human team member, just let me know. I'd like to gather some details to better understand your use case for querying historical logs via the Vercel CLI. Could you share: What specific log data you need your agents to access (function logs, build logs, edge logs, etc.) How far back in history you need to query logs What your current workflow looks like when agents need to access server logs Any specific CLI commands or functionality you've tried This will help the team understand the requirements for t

Pauline P. Narvas Thanks for reporting this feature gap! You're correct - while the AI SDK supports imageConfig for Google Gemini models (via PR #12059), this isn't currently available through the AI Gateway REST API. You could try the following workarounds though: Use the AI SDK with TypeScript (already supports this) If using BYOK, make direct calls to Google's API with imageConfig parameters Thanks again! Keep an eye out for updates :)

René Schubert Thanks for pointing to the PR, it helped me understand a bit more. However I’m not sure about the difference between and Is it basically the same and for both the structure of the providerOptions should be or does it differ, depending on whether I use @ai-sdk/google or not?

Pauline P. Narvas Thank you for your feedback, Jacob! We'll pass this onto our product team. For now, this is the new layout. Perhaps you'll get used to it?

Anshuman Bhardwaj Hi @zir, welcome to the Vercel Community! I'll pass on this feedback to our team.

Pauline P. Narvas Appreciate the feedback, Geraldo! I'll pass onto our domains team.

Pauline P. Narvas Thank you for sharing, @arunvitto-8473! We're currently working on improving the templates - thank you for your patience!

wfusn Experiencing almost the exact same thing when using the ShadCN registry approach with the components from our design system. It just started happening recently: Preview Not Supported. Things were working a few weeks ago (before Feb 2026). The LLM involved in the chat does not seem to be aware of what is going on in the preview window. Once you get past some initial install infra issues as mentioned by the initial reporter of this problem, it will report “No issues found” yet all you see is Preview Not Supported. Interestingly everything works if you go directly to the generated sandboxed NextJ

Jacob Paris Thanks for the feedback, I've passed it onto the dashboard design team! You can also promote to production from the main deployment list index, but I agree this button is hard to spot

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? oathe.ai/docs

Jacob Paris Skills Audits has launched here now skills.sh/audits

Amy Egan Good catch! Getting it fixed now. Thanks for reporting 🙏

Pauline P. Narvas This would be a great feature to add! Thank you for the feedback. We've let our product team know :)

Anshuman Bhardwaj Hi @parenthesesweb1-2378, welcome to the Vercel Community! Are you talking about v0 here or the Vercel platform? Can you share when was the last commit you pushed to the main branch? Is the person committing and pushing to GitHub part of your Vercel team?

Gil Seeing the same issue. Github has the latest commit (verified) and manually redeployed on Vercel but it doesn’t seem to pick up the latest version.

Gil fixed it! the problem was that my email for commits was different than my email for Vercel. Here’s how I fixed it: set the email for git for the project (this is from the project folder): git config user.email "your-vercel-email@example.com" then create an ‘empty’ commit because nothing has really changed: git commit --allow-empty -m "Force Vercel redeploy" and push it: git push origin main that did the trick

Pauline P. Narvas Thanks for the great feature request! I shared it with our product team. 🙂

Digital Eclipse Thank you for forwarding this to them! Please let me know if this ever gets worked on.

Anshuman Bhardwaj Hi @worknikolskii-2000, welcome to the Vercel Community! Thanks for sharing your feedback. I'll pass it on to our team and share here any updates that come.