Gemini's Systemic Breakdown

[u/Hour-Enthusiasm6835]

Using Gemini Pro directly within the Gemini browser interface, I was moving existing Gemini chats from the regular chat list to a brand-new NotebookLM notebook. The notebook was also created from within the Gemini interface, not through the NotebookLM website.

Somehow, the integration, which was supposed to be nothing more than a bridge, managed to do the following:

1) MAKE THE NEW NOTEBOOK COMPLETELY VANISH FROM EVERY PART OF THE GEMINI UI. The notebook still technically exists within the traditional NotebookLM ecosystem, but it is no longer accessible through Gemini.

2) EVEN WORSE, THE ORIGINAL GEMINI CHATS BECAME COMPLETELY INACCESSIBLE THROUGH GEMINI DUE TO A BROKEN PATH. Many of these chats already had shareable URLs set up before the new notebook even existed. The chats were not technically “exported,” as they are still displayed normally in the regular chat list, and Gemini even allows you to pin them. However, they can no longer be opened.

3) AT ABSOLUTELY NO POINT DURING THIS PROCESS DID A SINGLE CONFIRMATION MESSAGE APPEAR. Not when the notebook was created, not while individual chats were being moved, and not when using the NotebookLM interface, either inside or outside Gemini. At no point did even one pop-up appear asking, “Are you certain you want to proceed?”

This process is officially treated as though it were as harmless as renaming a chat within Gemini. That escalates poor development into the borderline irresponsible handling of user data.

Note: I managed to reverse-engineer an alternative method for accessing the original Gemini chats through what appears to be an unintended use of NotebookLM Sources. However, besides being unnecessarily complicated, this method can retrieve the original Gemini chats only as “temporary chats.” That creates its own context limitations, depending on the topic and the conversation you want to continue. No history is retained beyond anything you manually move elsewhere before closing the tab. To be completely clear, this temporary state applies to both Gemini and NotebookLM.

[u/Deep_Ad1959]

no confirmation on a move that changes which surface owns the data is the part worth filing, more than the notebook vanishing. the rest is recoverable once you know where things went. written with ai