@hamsa-ai/voice-agents-sdk 0.6.0-beta.5 → 0.6.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (8) hide show
  1. package/README.md +5 -4
  2. package/dist/index.cjs.js +1 -1
  3. package/dist/index.cjs.js.map +1 -1
  4. package/dist/index.esm.js +1 -1
  5. package/dist/index.esm.js.map +1 -1
  6. package/dist/index.umd.js +1 -1
  7. package/dist/index.umd.js.map +1 -1
  8. package/package.json +2 -2
package/README.md CHANGED
@@ -141,10 +141,11 @@ agent.end();
141
141
  | `end()` | End the chat session. |
142
142
 
143
143
  > **Note:** Use `chatMessageReceived` for chat UIs — it is dedicated to chat and
144
- > deterministic. The generic `messageReceived` event also fires for chat, but it
145
- > is dual-sourced (it additionally fires for voice transcriptions). In a
146
- > chat-only session the voice events (`answerReceived`, `transcriptionReceived`)
147
- > and audio events do not fire — the conversation lives entirely on the chat channel.
144
+ > deterministic. It surfaces the agent's text in chat-only sessions regardless of
145
+ > the underlying delivery channel. The generic `messageReceived` event also fires
146
+ > for chat, but it is dual-sourced (it additionally fires for voice
147
+ > transcriptions), so prefer `chatMessageReceived`. In a chat-only session the
148
+ > voice events (`answerReceived`, `transcriptionReceived`) and audio events do not fire.
148
149
 
149
150
  ## Advanced Audio Controls
150
151