Astro — install the widget

In an Astro site the tag goes into the layout every page uses, marked is:inline. The tag is the same on every platform — Install the widget has the general picture; this page has the exact place on Astro.

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 the layout every page uses (typically src/layouts/Layout.astro, or whatever your pages wrap themselves in).
2. Paste the tag just before </body> and add the is:inline directive to it: <script is:inline src="https://widget.guuey.com/v1.js" data-app="app_abc123" async></script> (your app id in place of app_abc123).
3. Build and deploy as usual.

• Why is:inline: Astro processes plain <script> tags by default (bundling, converting to type="module"); is:inline scripts are "rendered into the HTML exactly as written" — "no TypeScript and no import resolution by Astro" — which keeps the data-app attribute and the async flag on the tag the loader reads. Astro's docs show exactly this shape for external scripts.

Verified against the vendor's documentation on 2026-09-09: Scripts and event handling — is:inline and external scripts (docs.astro.build). 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 Astro site. Before changing anything,
read https://docs.guuey.com/embed/astro.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 the shared layout component (e.g. src/layouts/Layout.astro), just before </body>, with the is:inline directive on the tag so Astro emits it as written, 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.