chatkit-integration

To add authentication headers to ChatKit requests, you implement a custom fetch wrapper that injects headers like X-User-ID and metadata into the outgoing requests. This ensures your conversational interface securely identifies users before routing messages to agents.

You route ChatKit messages to custom agents by extending ChatKitServer and implementing the respond() method. This method loads thread history, extracts page metadata, builds a single prompt for your agents, and streams the generated responses back to the UI.

ChatKit integration supports multi-tenant isolation using RequestContext to separate user data. It provides conversation persistence, ensuring that authenticated users have their threads and history maintained independently across the web application.

The best way to inject page context is using a frontend integration that detects ChatKit script loading and extracts page content. It supports text-selection "Ask" flows, allowing authenticated learners to ask questions about specific selected content directly within Docusaurus apps.

Graceful degradation when ChatKit agent services fail is handled through production readiness features within the backend adapter. It ensures the conversational interface fails safely without crashing, maintaining application stability when domain-specific agents are unavailable.

You can use connection pool warmup to avoid long cold starts in ChatKit backends. This production readiness feature pre-initializes database connections, ensuring conversation persistence and agent routing respond quickly when the first user messages arrive.