TL;DR Add a configurable Standalone Full‑Page Mode so the site’s chat button can open a dedicated page (same domain or separate) instead of spawning an embedded/inlaid popup widget. This improves long‑form answers, reduces embed complexity, and provides a consistent experience across desktop and mobile without maintaining two separate code paths. Problem Many AI assistants return long and structured answers (tables, code, multi‑step guides). In a small, inlaid popup this is cramped and can feel slow or janky. On desktop, teams often prefer a full‑screen/browser tab where users can scroll, search, and share a permalink to a conversation. On mobile, the current widget can look fine, but maintaining different snippets or logic for widget vs page is error‑prone for implementers. Today, implementers sometimes hack around this by manually linking to an external chat app or building a second UI. Impact: Higher dev cost, inconsistent UX, reduced completion for long conversations, and poor shareability. Proposal Introduce a first‑class "Full‑Page (Redirect) Mode". Site owners can set the launcher button to redirect to a specified URL (same or cross‑domain) where the chat renders in full‑screen. Keep the existing inlaid widget as default; this adds a one‑line config choice. Goals & Non‑Goals Goals One configuration switch to choose Popup Widget or Standalone Full‑Page. Preserve conversation context and session continuity when launched via redirect. Support deep links with prefilled prompts (e.g., /chat?q=How+do+I+…). Provide analytics parity: open/close, session start, first token latency, message sends, deflections, and conversions. Non‑Goals Replacing the existing widget entirely. Building a new CMS; the full‑page UI can reuse the existing chat UI components. https://cdn.discordapp.com/attachments/1428878971675873280/1428878971902230619/Screenshot_2025-10-17_at_12.52.25_PM.png?ex=68f41abe&is=68f2c93e&hm=7d935579f7e7bcf246a8fc735464f702f1b0c23b817ed810ae7622f3bd7e47b6&

Full-page: https://botpress.com/docs/webchat/get-started/embed-in-element https://discord.com/channels/1108396290624213082/1272227414197669960

we tried it and it was buggy

You tried https://botpress.com/docs/webchat/get-started/embed-in-element and it was buggy? What was buggy? What unexpected behaviour did you notice?

It works on my side. Please post your JavaScript code and the Botpress code where you use User Data.

the spacing with the keyboard on mobile didn't work well, so we are using the built in web chat. the ideal would be webchat (default) for mobile since it goes full screen... then a full screen chatbot / embeded like for desktop

Use CSS with

media with

to set width of widget