Gemini Notebook moves into the chat with Connected App controls

What happened?

9to5Google reported on October 23 that Gemini Notebook is being exposed as a Connected App inside Gemini chats. The reported actions include creating, editing or deleting notebooks; adding, updating or deleting sources; listing notebooks and their sources; and answering questions using notebook context. Google’s help documentation confirms that users can ask Gemini to manage notebooks from a chat or task thread and that changes sync between Gemini Apps and Gemini Notebook.

The integration is not the same as universal availability. Google says Connected Apps are rolling out gradually, and its help pages say Gemini Notebook is available through the Gemini web and mobile apps. 9to5Google reported the new integration as enabled by default globally except in the European Economic Area, where it is off by default; Google’s documentation says EEA users may need to connect it manually.

Source: 9to5Google ↗ · Source: Google ↗ · Source: Google Gemini Notebook Help ↗ · Source: Google Gemini Apps Help ↗

The control surface matters

Google separately documents Connected Apps inside Gemini Notebook. In that interface, app access can be enabled or disabled for each notebook, and a change in one notebook does not carry over to another. That is a different control surface from enabling Gemini Notebook itself as an app inside Gemini. The documentation describes the notebook’s Connected App interface as web-only, while notebook content connected to Gemini Apps can be used on web and mobile.

Source: Google Gemini Notebook Help ↗ · Source: Google Gemini Apps Help ↗

Why does it matter?

Our analysis: this shifts Gemini Notebook from a place users visit into a context Gemini can act on during ordinary conversation. That is convenient for research and project work, but it also makes the boundary between asking a question and changing a knowledge store more important. Users should be able to tell when Gemini is reading a notebook, when it is adding a source and when it is making a destructive change.

The useful test is not how many actions the integration supports. It is whether the interface makes provenance and consent legible as the notebook becomes part of a larger assistant workflow. Rollout coverage, regional defaults and notebook-level controls are product details today; they will become trust features if the integration becomes a routine way to manage work.