@eshal-bot/chat-widget 0.1.68 → 0.1.70

package/dist/chat-widget.js

@@ -8777,23 +8777,19 @@
   };
 
   /**
-   * Constructs the voice WebSocket base URL — ALWAYS derived from the API
-   * base URL the widget is embedded with, as `wss://{host}/voice/ws`.
+   * Constructs the voice WebSocket base URL.
    *
-   * `/voice/ws/{org}/{session}` is terminated by the frontend custom server
-   * (packages/frontend/server.js), which proxies it in-cluster to
-   * knowledge-api on `/ws`. The widget always talks to the same origin it
-   * loaded its config from, so the WS endpoint is fully determined by
-   * `apiBaseUrl`. There is intentionally NO override parameter: voice can
-   * never be pointed at the (no-longer-public) knowledge-api LoadBalancer by
-   * a stale embed option or backend config value.
+   * If wsBaseUrl is provided (from agentConfig.wsBaseUrl in the deploy-agent
+   * response), use it directly — it points at the eshal frontend /voice/ws
+   * endpoint which proxies in-cluster to knowledge-api.
+   *
+   * For in-app use (apiBaseUrl IS the eshal frontend), derives from apiBaseUrl.
    *
    * @param {string} apiBaseUrl - Frontend base URL, e.g. https://demo.eshal.ai
-   * @returns {string} Voice WS base, e.g. wss://demo.eshal.ai/voice/ws
+   * @param {string} [wsBaseUrl] - Override from agentConfig, e.g. wss://dev.eshal.ai/voice/ws
+   * @returns {string} Voice WS base URL
    */
   const getWebSocketUrl = (apiBaseUrl, wsBaseUrl) => {
-    // If the backend returned a wsBaseUrl in agentConfig (or customer passed one
-    // explicitly), use it directly — it already points at the correct host.
     if (wsBaseUrl) return wsBaseUrl.replace(/\/$/, '');
     if (!apiBaseUrl) {
       return 'wss://dev.eshal.ai/voice/ws';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eshal-bot/chat-widget",
-  "version": "0.1.68",
+  "version": "0.1.70",
   "description": "Beautiful, embeddable chat widget with dark mode support",
   "type": "module",
   "main": "dist/chat-widget.js",