creamy-window-79763
03/04/2026, 12:40 PMtall-airline-16756
03/04/2026, 12:40 PMtall-airline-16756
03/04/2026, 12:40 PMAgent object.
The simplest approach is to read the agent’s session history via session.history on the AgentSession associated with the agent. session.history returns the full conversation history as a chronological list of messages (both user inputs and agent responses) and is the canonical source of truth for the transcript.
Example (Python):
# Access full conversation history from within the agent
full_history = context.session.history
If you need real-time updates as messages arrive, listen for the conversation_item_added event — it fires whenever a new message is added, letting you process or stream transcript items as they occur.
Notes:
• session.history persists across agent handoffs and contains the full transcript.
• The LLM chat context may be truncated, so rely on session.history for the complete record.
If you want, tell me:
• Which language or SDK you’re using (Python, JavaScript, etc.), or
• Whether you need the transcript in a specific format (plain text, JSON, or exported file), and I’ll provide a tailored code example. Sources: Building multi-agent architectures with LiveKit agents | LiveKit | Text and transcriptions | LiveKit Documentation