Skip to main content

Overview

Bring Onyx to your website with an embeddable chat widget. The widget is a standard web component, so it works with any website or framework. Your visitors can chat with an Onyx Agent without leaving your page.

Features

  • Lightweight - ~100-150kb gzipped bundle
  • Fully Customizable - Colors, branding, and styling to match your site
  • Responsive - Desktop popup, mobile fullscreen
  • Shadow DOM Isolation - No style conflicts with your existing CSS
  • Real-time Streaming - Server-sent events (SSE) for fast responses
  • Session Persistence - Conversations survive page reloads
  • Two Display Modes - Floating launcher or inline embed
  • Source Citations - Optional citation badges linking to source documents
  • Two Authentication Modes - A shared API key, or each visitor’s own identity token

Quick Start

Add these few lines to your website:
Always use a limited-scope API key for the widget. The API key is visible in client-side code, so it should have restricted permissions and rate limits. Never use admin or full-access keys.
The widget is available on all editions. Create the API key in Admin Panel > Service Accounts (/admin/service-accounts).

Display Modes

Launcher Mode (Default)

A floating button appears in the bottom-right corner.
  • Desktop: 400x600px popup above the button
  • Mobile: Full-screen overlay

Inline Mode

The widget embeds directly in your page layout.
The widget fills its container in inline mode. Give the container an explicit height; otherwise the panel grows with the conversation.
Before the first message, inline mode shows a compact input bar. Add start-expanded to show the full chat panel from the start:

Configuration Options

Required Attributes

Optional Attributes

include-citations and start-expanded are boolean flags. Their presence alone means true. include-citations="false" still turns citations on. Omit the attribute to turn it off.
Citations and private documents: When include-citations is enabled, the widget will cite any documents accessible to the configured agent or API key. If the agent has access to private or internal documents, citation links may point to resources that end users cannot view. Scope the agent’s document access appropriately, or disable citations for public-facing deployments with sensitive sources.

Configuration Examples

Basic Setup:
Full Customization:

Customization

Styling

The widget uses CSS custom properties for theming. Default Colors: Override via attributes:

Authentication

The widget sends a credential with every request. It gets that credential in one of two ways.

API key

Set the api-key attribute. Every visitor uses the same key, so all conversations run as one Onyx service account.

Visitor identity token (JWT passthrough)

Assign a tokenProvider function and leave api-key off. The widget calls it before every request, so your page controls expiry and refresh. Each visitor acts as their own Onyx user, and their document permissions apply. Use this when your page already signs the visitor in with the same identity provider as Onyx.
tokenProvider is a JavaScript property, not an HTML attribute. When both are present, tokenProvider wins.
JWT passthrough is for self-hosted, single-tenant deployments only. Your administrator must configure Onyx to accept the tokens. See the Website Widget Deployment Guide.

How it works

The widget talks directly to your Onyx server. It creates a chat session, sends each message, and streams the answer back in real time. Answers render with full Markdown support.

Browser Support

  • Chrome/Edge 90+ (Chromium)
  • Firefox 90+
  • Safari 15+
  • Mobile Safari (iOS 15+)
  • Mobile Chrome (Android)

Deployment

For detailed deployment instructions, including self-hosted setup and API key security best practices, see the Website Widget Deployment Guide.