How do I lock which sites can drive my embedded agent?
Open Share → Embed on your agent. With no domains listed, embeds keep working as before. Add https://yoursite.com or https://*.yoursite.com to restrict who can drive the chat via postMessage. Same-origin and tryanakin.app always work. Unlisted parents are ignored with a console warning — visitors can still chat; only framing commands are blocked.
Frequently asked questions
Will my existing embeds break today?
No. An empty allowlist is legacy mode: any site may still embed and drive the chat (shape validation still applies). Behavior only tightens after you add at least one domain.
What formats are accepted?
Exact origins like https://acme.com, or a single subdomain wildcard like https://*.acme.com. Paths, query strings, and http (except localhost in development) are rejected.
Does this block visitors from chatting?
No. Visitors can still open the agent and chat. The allowlist only gates parent-page postMessage commands (context, reset, prefill) from origins you did not list.
Where do I manage the list?
Agent Share modal → Website tab → Allowed domains. Add and remove entries there; changes apply on the next embed page load.
Sources: live catalog, resource model, integration guide.