Skip to content
ChatGPT · Google · Claude CodeEpisode 104 · 5 April 2026 · 58:16

Google Offers to Move Chats Out of ChatGPT: Memory Is Becoming the Main Way to Keep a User

What to watch for

1Compare “Google Offers to Move Chats Out of ChatGPT: Memory Is Becoming the Main Way to Keep a User” with “Transferring chats from other AIs: how practical is it?”: they provide different criteria for judging the same issue.
2Test the conclusion from “ChatGPT disappoints” in your own use case—what actually changes in the process and what remains a promise.
3Before choosing a product or approach, record the constraint identified in “The idea: transferring thinking into AI — a new startup?”.
4Define the owner of the outcome and the quality metric for the situation described in “Gemini update: importing chats from ChatGPT and Claude”.
Signals to track afterwards
Watch for actions by Anthropic and Google that confirm or challenge the episode’s central claims.
Compare new launches and policy changes with “ChatGPT disappoints”: have access, quality, price, or constraints changed?
Check whether the scenario in “Gemini update: importing chats from ChatGPT and Claude” becomes repeatable practice rather than a one-off demonstration.
Most useful for
Executives and managersDevelopersAI usersEntrepreneursProduct teamsProcess owners

Key takeaways

00:00Google offers to import chats from ChatGPT and Claude because memory has become a new barrier to switching products

In the context of “Google Offers to Move Chats Out of ChatGPT: Memory Is Becoming the Main Way to Keep,” this criterion applies: a person may have spent years explaining a business, habits, and style to a model. Starting in another system means raising a digital conversational partner from zero again.

03:01Who owns the outcome: the Anthropic code leak (Claude Code) — what it means

The boundary of the “Anthropic code leakage (Claude Code): what does that mean, part 2/2” case is defined by this point: the leak shows that code and development context are also memory: an exposed codebase reveals accumulated engineering value and dependencies, so the risk is what a competitor or an attacker can reconstruct.

05:11What changes in real work: what Claude Code is — the interface and the model's brains

The practical meaning of “What is Claude Code: Interface, model brains” is that the value is not the interface but the model doing real work with code under review and constraints; the tool proves itself through reliable daily work, not a demo.

07:50Why context matters more than one metric: what the code leak changes for the market and competitors

The working conclusion from “What the code leak changes for the market and competitors” is that a leak lets competitors see accumulated engineering value, so Google's move is to promise to take that value over, and portability becomes the real battleground.

09:12How the issue moves from news to product: the Gemini update — importing chats from ChatGPT and Claude

The practical meaning of “Gemini update: importing chats from ChatGPT and Claude” is that memory has become a barrier to switching products — years of accumulated context — so importing chats lowers that barrier, but a transfer drags along far more than facts.

11:44The practical meaning: how Google's chat import works

In the context of “How Google's chat import works,” this criterion applies: technically it is export-and-upload, but a chat contains mistakes, old decisions, emotional conversations, and accidental phrasing, and the new model may build a psychological profile the person never approved.

13:16Where the promise meets reality: a psychological profile from ChatGPT

The “A psychological profile from ChatGPT” scene leads to a working conclusion: access to all chats makes it possible to imitate the user's logic and style — useful for a personal assistant and dangerous in a leak, an account sale, or use of the data by someone else.

27:33The idea of a “personality snapshot” is especially sensitive

The “Transferring chats from other AIs: how practical is it?” topic becomes clearer once this point is included: access to all chats makes it possible to imitate the user’s logic and style. That is useful for a personal assistant and dangerous in a leak, an account sale, or use of the data by someone else.

36:24Disappointment with ChatGPT increases the desire to migrate: quality changes, memory mixes contexts, and new models are not always better at a familiar task

The “ChatGPT disappoints” scene leads to a working conclusion: disappointment fuels migration — quality shifts, memory mixes contexts, and new models are not always better at a familiar task — but a transfer should not become an unfiltered copy of an entire life.

43:20The Claude Code leak is a reminder that code and development context are also memory

The decision in “The idea: transferring thinking into AI — a new startup?” depends on one criterion: trust in personal AI is not a privacy promise but controllable permissions, retention periods, and the ability to revoke access — that is what makes transferring your thinking safe or not.

What this episode is about

Importing conversations promises to preserve context when someone changes models, but the transfer includes a psychological profile, business logic, and personal history. A Claude Code leak and frustration with ChatGPT show why users want to leave—and why doing so safely is harder than exporting a file.

Google offers to import chats from ChatGPT and Claude because memory has become a new barrier to switching products. A person may have spent years explaining a business, habits, and style to a model. Starting in another system means raising a digital conversational partner from zero again.

Technically, the transfer looks simple: export an archive and upload it to Gemini. But a chat contains more than facts. It contains mistakes, old decisions, emotional conversations, and accidental phrasing. The new model may construct a psychological profile the person never approved themselves.

The idea of a “personality snapshot” is especially sensitive. Access to all chats makes it possible to imitate the user’s logic and style. That is useful for a personal assistant and dangerous in a leak, an account sale, or use of the data by someone else.

Disappointment with ChatGPT increases the desire to migrate: quality changes, memory mixes contexts, and new models are not always better at a familiar task. A transfer, however, should not become an unfiltered copy of an entire life. Projects, personal conversations, and work data need to be separated.

The Claude Code leak is a reminder that code and development context are also memory. Google is trying to win not only with a model, but by promising to take over a competitor’s accumulated value. Real portability arrives when the user can inspect, edit, and selectively move a profile—not when they hand a new company an enormous archive and hope it understands them correctly.

Trust in personal AI is determined not by a privacy promise, but by controllable permissions, retention periods, and the ability to revoke access.

Episode transcript

The episode is in Russian; below is an English reading guide to the transcript (the full EN transcript is a machine translation). Voice matching applied to 133 segments: 46 identified, 5 mixed, 38 probable, and 44 unresolved.

Loading…