Skip to main content
Client events help an interface distinguish user input, agent output, interruptions, and tool activity. The configuration can store event selections, but a verified Threetone client subscription API is not established by the documented runtime.

​
Review the event selection

The schema includes names such as user_transcript, agent_response, interruption, client_tool_call, agent_tool_response, and context_usage. Use Update agent to inspect the exact accepted selection under conversation_config.conversation.client_events. Keep the selection focused on the interface’s needs. Transcript and tool data can include private information. Define which events are displayed, retained, or excluded from logs before the channel is enabled.

​
Prepare handlers

Do not invent a socket URL, payload envelope, or onEvent SDK method. Add runnable handlers when those contracts are released and tested.

​
Frequently asked questions

A saved selection does not prove emission. Conversation initiation and execution remain separately gated.
Use controlled data and retain only what the test needs. Keep credentials and unnecessary transcript content out of application logs.