@hamsa-ai/voice-agents-sdk 0.6.0-beta.2 → 0.6.0-beta.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hamsa-ai/voice-agents-sdk",
-  "version": "0.6.0-beta.2",
+  "version": "0.6.0-beta.4",
   "description": "Hamsa AI - Voice Agents JavaScript SDK",
   "main": "dist/index.cjs.js",
   "module": "dist/index.esm.js",

package/types/classes/livekit-tool-registry.d.ts

@@ -500,7 +500,16 @@ export declare class LiveKitToolRegistry extends EventEmitter {
      * Synthesizes a stable id when the source segment lacks one so consumers can
      * still key the message, and stamps the observation time.
      */
+    private buildReceivedMessage;
     private emitMessageReceived;
+    /**
+     * Emits a chat message originating from the {@link LIVEKIT_CHAT_TOPIC} stream.
+     *
+     * Fires the dedicated `chatMessageReceived` event — which fires only for real
+     * chat messages, never voice transcriptions — and, for backward
+     * compatibility, the generic `messageReceived` event with the same payload.
+     */
+    private emitChatMessage;
     /**
      * Returns the count of currently registered tools
      *

package/types/main.d.ts

@@ -216,8 +216,23 @@ type HamsaVoiceAgentEvents = {
      * with structured, streaming-aware metadata (id, role, isFinal, timestamp).
      * Use this to drive a chat UI; prefer it over the plain-string
      * `answerReceived`/`transcriptionReceived` events when rendering message bubbles.
+     *
+     * Note: this is dual-sourced (chat text streams AND voice transcriptions).
+     * For a chat-only integration, prefer {@link chatMessageReceived}.
      */
     messageReceived: (message: ReceivedMessage) => void;
+    /**
+     * Emitted only for chat messages received on the chat text-stream channel
+     * (`lk.chat`) — agent replies and the greeting in chat-only sessions.
+     * Same `ReceivedMessage` shape (stable id for in-place updates, streaming
+     * partials with `isFinal: false` followed by a final `isFinal: true`).
+     *
+     * Unlike {@link messageReceived}, this never fires for voice transcriptions,
+     * so it is the deterministic event for chat UIs. Pair with `agentStateChanged`
+     * for a typing indicator. In chat-only sessions, `answerReceived`,
+     * `transcriptionReceived`, and audio events do not fire.
+     */
+    chatMessageReceived: (message: ReceivedMessage) => void;
     /** Emitted when agent starts speaking */
     speaking: () => void;
     /** Emitted when agent is listening */