Chat widget configuration - Circuit

All widget configuration is server-side. You set options in the Circuit admin UI, and the launcher fetches them at page load via GET /chat-bot/config. There are no URL parameters beyond apiKey.

Where to configure

Everything is on the agent’s Chatbot settings page in Circuit:

Chat Widget HTML: the copyable <script> tag and CSP directives.
Allowed Website Domains: the chip input where you add hostnames that may embed the widget.
Test on this page: a toggle that adds the current admin-page host to the allowed domains list and injects the launcher so you can preview the widget without leaving Circuit.
The remaining fields (name, welcome message, position, style, attribution, primary color, logo) appear in the chatbot appearance section of the same page.

Configuration fields

Field	Source	Description
Name	Chatbot key	Display name shown in the widget header. Defaults to the agent’s name when not set.
Welcome message	Chatbot key	Greeting shown when the chat window opens before the first message. Leave blank for no greeting.
Primary color	Agent record	Background color of the launcher bubble and accent color inside the chat.
Logo	Agent record	Image shown on the launcher bubble. Falls back to the Circuit mark when not set.
Position	Chatbot key	Corner of the page where the bubble and chat window appear. Options: `bottom-right`, `bottom-left`, `top-right`, `top-left`, `bottom-center`, and others. Unrecognized values fall back to `bottom-right`.
Style	Chatbot key	`windowed` renders an opaque bordered pane. `floating` renders individually floating cards that hover over the host page. Defaults to `windowed`.
Attribution	Chatbot key	Shows a Circuit branding footer inside the chat. On by default.

How changes propagate

The config response is cached for 60 seconds (Cache-Control: public, max-age=60, Vary: Authorization, Origin). Appearance changes you save in the admin UI appear on embedded sites within 60 seconds. To see a change immediately during testing, hard-reload the page to bypass the cache.

What is not configurable

The widget does not support custom fonts, custom CSS, hiding built-in controls, or programmatic configuration via URL parameters. See the overview for the full limitations list.