How does the conversational agent handle memory conversation history?

[mighty ice]

AI-generated Answer for davidtmp

The conversational agent does not retain memory or conversation history globally. Instead, it uses dynamic conversation settings that allow you to override the agent's configuration at the start of each session. These settings apply only to the current session and do not persist across conversations.

If you need to update the agent's context or system prompt during a session, you must make a separate API call, as changes made mid-conversation won't take effect until a new session begins.

[runic elbow]

so if we want to give the agent a sense of history, we should feed it the conversation/history when starting the agent?

[mighty ice]

AI-generated Answer for davidtmp

Yes, to give the conversational agent a sense of history, you would need to include the relevant conversation history or context at the start of each session. This can be done by structuring the system prompt or dynamically overriding the agent's configuration at the beginning of the conversation. However, these settings will only apply to the current session and won’t persist globally.

If you need to update the agent's context during a session, you must make a separate API call, as agent settings cannot be updated through the same WebSocket connection used for audio chunks and pong messages. Keep in mind that changes to the system prompt or agent settings mid-conversation will only take effect in new sessions.

[runic elbow]

what is this api call?

[mighty ice]

AI-generated Answer for davidtmp

The provided context does not include information about how the conversational agent handles memory or conversation history, nor does it specify an API call related to this functionality. You may need to consult the API References or provide more details about your requirements.

[runic elbow]

how can I pass dynamic (secret variables) to the when creation a custom mcp server connection for a conversational agent?