Key takeaways
- Google announced temporary threads for AI Mode in Search on November 17, 2026, rolling out globally on desktop and mobile browsers in supported AI Mode languages.
- Google says these responses do not use past preferences, affect future personalization or get saved to account history.
- Users enter through an icon in AI Mode’s upper-right corner, without changing their settings; closing the thread ends it, according to Google.
- The announcement does not specify backend retention, training exclusions, a new model/API identifier, pricing or numeric usage limits. AccessAllGPT has not tested the feature.
What Google announced
Google announced on November 17, 2026 that temporary threads are rolling out in AI Mode in Search. The feature lets a user ask a one-off question without saving it to history or carrying its subject into future personalization, according to Google. Availability is described as a global rollout on desktop and mobile browsers, across all languages supported in AI Mode.
The announcement gives no separate price, numeric query allowance or model/API identifier. This is a user-facing AI search feature, not a new inference endpoint or model release. A global rollout statement also does not prove the control is already visible in every eligible account. We have not signed in to verify individual access.
How a temporary thread differs from an ordinary search
Google directs users to the temporary threads icon in the upper-right corner of AI Mode. There is no need to adjust settings: enter a temporary thread, ask questions, then switch back when finished. Google’s examples are brainstorming a surprise gift and looking up something a user does not want resurfacing later in history or recommendations.
The company describes the session as completely detached from the account and makes three concrete promises about the experience: responses will not be informed by past preferences, will not affect future personalization and will not be saved to history. Google also says that once the thread is closed, it is gone. Those are vendor statements; we have not measured their implementation.
Our analysis: the trade-off is useful separation at the cost of personalized context. Someone who wants a fresh answer can choose a temporary thread. Someone who expects AI Mode to remember preferences should not assume those preferences will follow them into it.
History controls are not a complete retention policy
The announcement explains visible history and personalization behavior, but does not specify a backend retention period, logging exceptions, human-review rules, model-training exclusions or data residency. Its statement that a closed thread is gone should not be expanded into an independently verified claim that every server-side record is immediately deleted.
Nor does this brief establish anonymous browsing, an enterprise confidentiality agreement or permission to submit sensitive workplace information. A reader deciding whether to use the feature for confidential material needs the applicable product policies and organizational approval, not just a missing history entry.
The stated rollout covers desktop and mobile browsers. The post does not separately establish access in every native Google app, region-specific eligibility or identical availability for managed accounts. We do not infer those details from the word globally.
What to try next
For a low-risk first check, use a public, non-sensitive question that does not need your past preferences. Confirm the temporary-thread control is present, then compare the experience with an ordinary AI Mode conversation. Close the temporary thread and inspect the history interface. This can check visible behavior on your account; it cannot establish backend deletion or training treatment.
For AI product buyers, the broader lesson is to ask which kind of memory a control actually changes: the current conversation, saved history, personalization or service-side retention. Google’s launch is specific about the first three experience-level effects and leaves the retention-policy questions unanswered in this announcement.
Choose the right search session
A reader checklist, not a test AccessAllGPT performed.
Entries stay in this browser tab and are not submitted to AccessAllGPT. Blank responses are copied as [Unresolved].
Choose a temporary thread when you do not want the query saved to history or influencing future personalization.
Use the ordinary experience when the answer should draw on past preferences; Google says temporary threads exclude them.
Check the applicable retention and data-use policies first. A history control alone does not establish confidentiality.
Look for the upper-right icon in AI Mode on a desktop or mobile browser; a rollout can reach accounts at different times.
Primary sources
Browse the publication-wide evidence index →
- Temporary threads are now available in AI Mode in SearchGoogle · Reviewed: November 17, 2026 publication date; full announcement; icon and settings instructions; account detachment, history and personalization statements; global browser and language rollout scope · Retrieved · Supports: Google’s dated rollout announcement, described user flow and promised history/personalization behavior. Does not establish backend retention, training exclusions, pricing, numeric usage limits or independently verified account availability.
Limitations
No authenticated AI Mode session, hands-on comparison, account-history inspection, network capture or retention audit. Rollout and personalization behavior are Google’s claims. The announcement does not specify backend retention, training exclusions, usage limits, pricing, native-app eligibility or a new model/API identifier.
Disclosures
AccessAllGPT received no payment, private access or vendor review for this briefing. Google did not review or endorse it. AccessAllGPT Research is operated by NeuralArc; publication-wide relationships are listed on the disclosures page.


