Expand description
Client → Server message types for the Gemini Live wire protocol.
Structs§
- Activity
End - Marker for speech activity end.
- Activity
Signal Message - Activity signal for client-side VAD events.
- Activity
Signal Payload - Payload for activity signals.
- Activity
Start - Marker for speech activity start.
- Client
Content Message - Client content message for sending text or conversation history.
- Client
Content Payload - Payload for client content.
- Context
Update Message - Mid-session preamble update message (
contextUpdate). - Context
Update Payload - Payload of a
contextUpdatemessage. Unset fields are left off the wire, which is what keeps their current values on the server. - Context
Update Tools - The
toolswrapper of acontextUpdate. Its presence means “replace”: the list is always serialized, so an empty list clears every tool. - Media
Chunk - A single chunk of media data (audio). Deprecated — use Blob in
audiofield. - Realtime
Input Message - Realtime audio input sent as a stream of chunks.
- Realtime
Input Payload - Payload for realtime audio input.
- Setup
Message - Top-level setup message sent immediately after WebSocket connect.
- Setup
Payload - Payload of the setup message.
- Tool
Response Message - Tool response message sent after executing function calls.
- Tool
Response Payload - Payload for tool response.