Gemini 3.8 Live: separate a spoken answer from a completed action
Live dialogue can coordinate tools, but confirmations must come from the actual action result, especially when a conversation is interrupted.
In brief
Gemini 3.8 Live and Extended Thinking support live dialogue and tool-based work. A spoken “done” should still be checked against the tool result rather than accepted as proof of a booking or change.
This keeps a natural conversation from hiding failed actions, misunderstood details or duplicate requests.
Clarify what the assistant should do
“Find a suitable time” and “book it” have different consequences. State which you want and which connected account is intended. Review the visible plan if recipients, cost or irreversible changes matter.
Handle interruptions without duplication
If the conversation cuts out, check whether the external action completed before asking for it again. A repeated instruction can create a duplicate if the first request succeeded. Use the official application’s current state as the reference.
Keep precise details visible
Ask for a written confirmation of names, times, timezone and result identifiers where supplied. Correct misheard terms immediately. Natural audio does not remove the need to verify source information or a failed tool response.
Before you act
Feature access depends on the product and integration. A live demonstration is not proof that every account has the same tools or that an action is authorized.
What to do next
- Choose a supported task and state whether it is information-only or an actual action.
- Confirm important dates, names and recipients in text.
- Inspect the action result and current state before repeating a request.
