Skip to main content

Basic Usage

During a persona session, you can force a response from the persona using the talk method. This is useful when the user interacts with a UI element or when you use your own LLM instead of Anam’s built-in models.
Both talk() and createTalkMessageStream() require an active streaming session. Call stream() or streamToVideoElement() first.
This sends the text to the persona, which then speaks it aloud.
To learn more about using the talk method with your own LLM, see the Custom LLMs guide.

Streaming Talk Input

For lower latency, stream messages to the persona in chunks. This works well when streaming output from a custom LLM.
Each TalkMessageStream represents one conversation turn. Once the turn ends, create a new stream for the next turn.

Available Methods

The TalkMessageStream object provides these methods:

Streaming Multiple Utterances

With @anam-ai/js-sdk version 4.26.0 or later, you can divide one TalkMessageStream into ordered utterances. A new utterance waits for the previous one to finish playing while both remain part of the same conversation turn. This lets the persona speak before a tool call and continue when the result is ready.
Multi-utterance talk streams require a Cara 4 avatar. With Cara 3, the persona still speaks the text, but Anam treats the stream as one utterance and does not return your utterance IDs. The SDK does not throw an error or warning.
Pass an utteranceId as the third argument on the first chunk of each utterance. The ID must be a lowercase UUID v4; crypto.randomUUID() returns the required format. The method throws before sending the chunk if the ID is invalid. Omit the ID from later chunks in the same utterance.
The IDs are returned in persona MESSAGE_STREAM_EVENT_RECEIVED events as utteranceId. Use them to match streamed captions to the utterances you sent. See Listen for JavaScript SDK Events for the event payload.
Send the next text chunk within 15 seconds. After 15 seconds without a chunk that contains text, the server closes the stream and rejects later chunks with the same correlation ID. Empty chunks do not reset the timeout. For a longer tool call, end the first stream and create a new one for the result.

Ending a Stream

End a conversation turn in one of two ways: Option 1: Set endOfSpeech on the last chunk
Option 2: Call endMessage() separately

Handling Interruptions

When a user speaks during a stream, the SDK emits AnamEvent.TALK_STREAM_INTERRUPTED and closes the stream:

Checking Stream State

Check whether a stream can still accept chunks:

Error Handling

The streamMessageChunk method throws an error if the stream is not active:

Correlation IDs

Attach a correlation ID to track streams, especially useful for matching interruption events:
Use unique correlation IDs for each TalkMessageStream. The ID appears in TALK_STREAM_INTERRUPTED events, helping you identify which stream was interrupted.

Next Steps

Audio Control

Learn how to control audio input in your Anam sessions
Last modified on August 26, 2026