Vite — install the widget

In a Vite app the tag goes into the one HTML shell every route renders in. The tag is the same on every platform — Install the widget has the general picture; this page has the exact place on Vite.

The tag

The tag — put your app id in place of app_abc123

<!-- guuey widget. Add this site to the app's allowed domains or the embed is refused. -->
<script src="https://widget.guuey.com/v1.js" data-app="app_abc123" async></script>

Where it goes

1. Open index.html at the project root: Vite treats it as "the entry point to your application", "front-and-central instead of being tucked away inside public".
2. Paste the tag just before </body> — it can sit right after the module script tag Vite already has there — and save.
3. Build and deploy as usual — a single-page app serves this one file for every route, so the launcher covers the whole app.

• Because every route renders inside this one shell, the launcher follows client-side navigation; to hide it on some routes, use the hiding pattern on Embed & share.
• Create React App projects (its own docs now carry the header "Create React App is deprecated"): the HTML file lives in the public folder — "The public folder contains the HTML file so you can tweak it" — and the tag goes there, before </body>.

Verified against the vendor's documentation on 2026-09-09: Getting started — index.html and project root (vite.dev) · Using the public folder (Create React App docs). Vendor interfaces change — if a step no longer matches what you see, the vendor's page above is the source of truth.

Before it shows

Allow your site’s origin (console → Embed → Allowed origins, or guuey apps update <appId> --domains <origin>; about 15 seconds to apply), add the CSP allowances if your site sets a policy, then verify with guuey apps check <appId> --origin <origin> — the steps are on Install the widget.

Give this to your coding agent

Paste into your coding agent

Install the Guuey chat widget on this Vite (React, Vue, Svelte, and other single-page apps) site. Before changing anything,
read https://docs.guuey.com/embed/vite.md and https://docs.guuey.com/install-widget.md
(the raw markdown of the two pages) and follow them exactly; do not invent options
or steps they do not contain.

1. Put this tag in index.html at the project root (Vite's entry point), just before </body>, with my app id <appId> in place of app_abc123:
   <script src="https://widget.guuey.com/v1.js" data-app="app_abc123" async></script>
   Add nothing else to the tag — except your page's CSP nonce, if the site uses
   nonces (step 3).
2. Tell me the exact origin(s) my pages are served from (scheme + host) so I can
   add them to the app's allowed domains in the console (Embed → Allowed origins)
   or with: guuey apps update <appId> --domains <origin>. Remind me that a bare
   hostname covers the apex and every subdomain, while a scheme-prefixed origin is
   an exact match, and that changes take about 15 seconds to apply.
3. If this site sets a Content-Security-Policy, add exactly these allowances and
   nothing more. If the policy uses nonces (script-src 'nonce-...'): render the
   site's per-request nonce on the widget tag the way its other script tags carry
   it — that is what lets the loader run, and the loader puts the same nonce on the
   one <style> it injects; then allow https://widget.guuey.com in frame-src and
   connect-src. If the policy uses host allowlists: add https://widget.guuey.com to
   script-src, frame-src and connect-src, and 'unsafe-inline' to style-src.
4. When I've saved the origin, verify with:
   guuey apps check <appId> --origin <origin>
Stop and ask me before any step those two pages do not describe.