- Shipped
- September 5, 2026 at 8:32 PM UTC
- Author
- Kamo
- Commit
- be6b3eb
The chat key is per-PRODUCT, not per-deployment. A lender picks a web chat integration when they publish an application, and the public endpoint resolves that integration's key from the product id in the URL — so the widget moves out of the root layout, which cannot know which application is being read, and into the two pages that do. The deployment-wide PUBLIC_CHAT_API_KEY is gone with it. One env var could only ever name one org's key on a site that serves all of them; the configmap now says so where an operator would go looking for it. Renders nothing when the lender has not attached an integration, or when theirs was deleted or switched off. The application matters more than the bubble — a borrower who cannot apply because a chat widget is misconfigured is the worst of the three outcomes.