Chkampouri 5022 Update: the fix I described above (splitting into Server/Client components with Suspense scoped to just the form) turned out to be incomplete. The page still appeared empty to fetch-based crawlers, because any use of the searchParams prop (even just reading it) forces the whole route to be dynamically rendered — which seems to be what actually broke crawler visibility, not the Suspense boundary itself. The real fix: remove searchParams entirely from the Server Component, and read the URL parameter purely client-side via window.location.search inside the Client Component's useEffect. This lets

integrations01-takeb We have the same issue. Containers go cold under 30s.

Ryu Hi Vadym, This looks like a mobile viewport/keyboard layout issue rather than something specific to your prompt. The useful details to add for whoever triages it would be: From the repro steps, it sounds like the Ask AI panel/input is not recalculating correctly when the iOS keyboard appears, so the input area gets pushed or clipped in the visual viewport. A temporary workaround would be to use the docs Ask AI flow from desktop/tablet, or try Safari vs Chrome on the same iPhone to see whether it is WebKit/iOS-wide or browser-specific. If you can, I’d also add whether the screenshot was taken a

Vadym Kotai iPhone 16 Pro Max iOS 26.5 Browser Safari - version that is bundled with iOS 26.5 Doesn’t happen all the time - only sometimes when I try to focus the text area, it jumps randomly up. Sometimes to the middle of the screen, sometimes stays the bottom, sometimes jumps up, and only half of it is visible. When I rotate the screen - the ai chat is displayed on the right side and there is no jump Regarding Chrome - this never happens. The behavior in chrome is stable - it always jumps to to the same place like on the screenshot attached and the full area is always visible

Ryu Hi Vadym, Thanks, that detail helps. Since it is intermittent on iPhone Safari and only happens while focusing the textarea, this sounds even more like a visual viewport / keyboard resize race rather than a static CSS breakpoint issue. The landscape behavior is useful too: if the panel moves to the right side in landscape and no longer jumps, then the bug is probably specific to the bottom-sheet/mobile layout. I’d add this as the clearest repro summary: If you can reproduce it again, a short screen recording would probably be more useful than another screenshot because the bug is about the tex

Amy Egan Thanks for the feedback! Yes, this is something others have also run into. It's expected behavior for now, as you saw in the docs. vercel.com/docs/monorepos#requirements Changing that behavior is more complex than it might seem at first glance, so we don't have an immediate solution. But I shared this thread with the team and I'll keep it open so others can share their experience and suggestions 😃

Amy Egan Also want to share another workaround I've seen. You can build a custom workflow to have more control over exactly what gets deployed and avoid the canceled deployments. There's a basic script template and setup steps for GitHub Actions in this guide: vercel.com/kb/guide/how-can-i-use-github-actions-with-vercel That's obviously a bit more work than the standard automatic deployments. But once you've got it set up it just works. I hope that helps!

Timothy Thanks for the suggestion! I'll probably end up going with GitHub actions for now. I definitely would love to see some work on the skip unaffected deployments feature to be a bit more controlled, especially since polyglot monorepos are more and more popular these days. I do think some more control based on these environments would be welcome.

Ryu Hi SkyMesh Dynamics, This is a real edge case, but I’d frame it as DNS/TLS/host normalization rather than an HTTP routing issue. A trailing dot is valid in DNS because it represents the fully qualified domain name: But for HTTPS there is another layer before HTTP routing: TLS certificate selection via SNI. If the browser/client sends the SNI/host as vercel.com. and the edge does not normalize it to vercel.com before certificate/host matching, the request can fail before the app or redirect logic gets a chance to run. You can compare both cases with: If the no-dot version succeeds and the trail

Ryu Hi Asuileman, That error sounds like it may not be coming from the normal Vercel Project Settings → Domains flow, because a Vercel project is not generally limited to only one custom domain on Hobby. I’d first check where you are adding it: Then try adding the domains separately, for example: If the dashboard says you cannot add more than one domain but the domain does not appear, check whether the domain is already attached somewhere else in the same team: If it shows as assigned to another project, remove it from the old project first or reassign it from the correct project/team. If it does

Abhishek23 Would love to see 15s support for Seedance 2.0 and Seedance 2.0 Fast on Vercel AI Gateway. Other providers already support 15s for these models, so matching that limit would make Gateway much more useful.

Ryu Hi Gabriel, I think keeping @vercel/related-projects server-side is probably the safer default. The package reads VERCEL_RELATED_PROJECTS, and exposing that automatically to the browser would turn deployment/project mapping metadata into public client-side data. For your use case, I'd put a very small server wrapper in front of it instead of trying to call the package directly from the browser. For example, in a Next.js Route Handler: Then the browser calls your own route: That lets you expose only the specific URL the client needs, without exposing the full related-projects payload or other d

Amy Egan Are you talking about v0 credits? Those do roll over to the next month 😃 Here's a screenshot from my test team where you can see all the credits from the previous month rolled into the current one.

Arthurjoel12 I mean with vercel