Embed a web chat widget

Put a public AI chat widget on your own website — create a web channel, embed one script, and choose session, login, and read-only behavior.

Turn any agent into a chat widget for your own site — a support assistant, a sales bot, an interactive demo. The web channel gives you a public chat page and a one-line embed snippet; visitors talk to your agent right where they already are, no login required unless you want one.

A web chat session with a Buda agent

Create a web channel

Add the channel

Open Settings → Channels, click Add Channel, and select Web. Pick the target agent that should answer, give it a label, and save.

Open its configuration

Select the new web channel to open its config panel. It gives you the public chat link, the embed snippet, and the visitor toggles described below.

Each web channel has two ways to go live:

Public chat link — a hosted page at https://your-buda-domain/c/<channelId>. Copy it and share it directly, or link to it from a button.
Embed snippet — drop this script into your site's HTML and the widget loads automatically:

<script>
  (function() {
    var s = document.createElement('script');
    s.src = 'https://your-buda-domain/embed.js';
    s.dataset.channelId = '<channelId>';
    document.head.appendChild(s);
  })();
</script>

The config panel generates both with your real domain and channel ID filled in — use the copy buttons rather than typing them by hand.

A web channel only serves visitors while it's active. If the chat page shows "not found", check the channel status in Settings → Channels.

Visitor behavior

Three toggles in the config panel control how visitors experience the widget. They apply instantly.

Persistent vs new session

Persistent — a returning visitor lands back in the same conversation, so context carries across visits. Best for ongoing support or a personal assistant.
New each visit — every visit starts a fresh chat session with no prior history. Best for one-off questions, demos, or kiosks where you don't want one person's chat bleeding into the next.

Anonymous (default) — anyone with the link can chat without signing in.
Require login — visitors must sign in first. Their name appears on the session, which is useful when you want to attribute conversations to real users.

Read-only mode

Turn on read-only to let visitors view an existing conversation without being able to send messages — handy for sharing a finished thread or showcasing an agent's output without opening it up to new input.

Channels overview — how channels route messages to agents
Chat session — how persistent and new-session modes map to sessions