Thanks — I’m responding to your question about whether you can get the latest message in a LiveKit conversation when multiple tools are being called in parallel. Yes — you can access the latest message even with parallel tool calls. Two straightforward ways to get it: • Use `session.history`:

session.history

is a chronological list of all conversation items (user messages, tool calls, and tool outputs). The latest message is the last item in that list, so read the final element of

session.history

. • Use `on_user_turn_completed`: inside an agent, the

on_user_turn_completed

lifecycle method receives a

new_message

parameter that represents the user’s most recent message. This method runs before the agent generates a response, so it’s a convenient place to access the latest input. If you need to access the conversation state from inside tool execution, the tool’s

RunContext

provides access to the session (and therefore

session.history

) so you can inspect the latest item there as well. Would you like a short code example showing: 1) how to read the last item from

session.history

, or 2) how to use

on_user_turn_completed

or

RunContext

inside a tool? Sources: External data and RAG | LiveKit Documentation | Pipeline nodes and hooks | LiveKit Documentation | Building multi-agent architectures with LiveKit agents | LiveKit