Install on your website
Embed the launcher once and control authorized websites and page display from the portal.
On this page
Before installation
An administrator needs access to Installation. Your website maintainer needs permission to edit the site's shared HTML template or equivalent site-wide script configuration.
The chatbot appears in an iframe launched by a small script. This isolates its interface styles from the host website. The installation is an embedded website chatbot, rather than a replacement for your website's existing forms or content.
Copy the installation script
In Installation, copy the script generated for your workspace. Add it once to the shared template used on the pages where the chatbot may appear, normally before the closing body tag.
An example has this structure:
<script src="https://preview.runsagents.com/launcher.js" data-tenant="your-workspace"></script>
Use your actual copied script. The example workspace identifier is a placeholder. Avoid inserting the script repeatedly when a single-page app changes routes.
Authorize the website origin
Add the website in Websites. An origin contains the scheme, hostname, and optional port, for example https://www.example.com. It does not contain a page path.
https://example.com and https://www.example.com are separate installation origins. HTTP and HTTPS, different subdomains, and different ports are also distinct. With no authorized websites, the chatbot appears on no external website.
Choose where the chatbot appears
| Display policy | Behavior |
|---|---|
| Every page | Display throughout the authorized origin. |
| Only these pages | Display on matching configured paths. |
| Every page except these pages | Hide on matching configured paths. |
A page rule matches This page or This page and subpages. A subtree rule for /support includes /support/contact, but not /supporters. Query strings and URL fragments do not select different display rules.
Dashboard changes do not require a new script. Configuration can be briefly cached, and an already open page does not receive a live policy push. Reload when verifying changes. On a single-page website, meaningful pathname changes re-evaluate whether the widget should appear.
Check loading and security policy
Allow the Runs Agents script origin in the host website's script policy and the chatbot origin in its frame policy when your site restricts those resources. The launcher also requests its public configuration. Have the developer inspect actual blocked requests rather than broadly disabling the site's Content Security Policy.
Embedding authorization is also enforced by the chatbot's frame policy. Direct iframe embedding does not replace the authorized website settings. A privacy extension, blocked storage, proxy, or browser policy can affect loading or restoration.
Verify the installation
- Open an allowed public page and check the launcher in desktop and mobile layouts.
- Open it, review the privacy notice, and send a synthetic question.
- Close and reopen it, then navigate and reload to check conversation and draft restoration.
- Check a page excluded by the display policy.
- Confirm the conversation appears in the correct workspace.
Save launcher position in Preview. To remove the embed, remove the script from your site's template; use website authorization and page rules to control display through the portal.