Status

What works right now

Google reships Gemini Notebook constantly, and every change can break an extension in this category. This page says what is verified to work, when a human last checked, and what we owe you when it breaks.

Extension version 1.5.0Independent check of 1.5.0 against Gemini Notebook pending

The patch commitment

If a change on Google’s side breaks capture or export, we ship a fix within 48 hours of confirming it.

  • It is a commitment about turnaround, not about Chrome Web Store review, which is out of our hands. The build goes out within 48 hours; the store publishes it when it publishes it.
  • Being one developer is what makes it possible. There is no release train to wait for.
  • When a break is confirmed, it appears in the known issues below before it is fixed, not after.

Compatibility

Checked by hand on the date above. This is a compatibility statement, not a live monitor — see the note at the end of this page.

Working

Gemini Notebook — notebook.google.com

Sending saved sources into a notebook

The current address, and the one the extension prefers.

Working

NotebookLM — notebooklm.google.com

Sending saved sources into a notebook

Google redirects the old address to the new one. The extension still recognises it, because open tabs and old bookmarks still point there.

Working

ChatGPT, Claude, Gemini, Grok, Kimi, Perplexity, YouTube, Reddit, X, LinkedIn, Google Docs

One-click capture from the page

Each of these has a purpose-built reader. Every one can be turned off individually in the popup.

Partial

Any other website

One-click capture from the page

Requires the optional all-sites permission, which is off until you grant it. Some staged-rendering sites capture less text — see the known issue below.

Working

Markdown, LaTeX, JSON, plain text

Exporting your library

Export files are assembled in your own browser from sources already in your library.

Known issues

Open defects you could hit today. This is not a roadmap, and it is not a place feature requests go to wait.

Fix in progressOpen since 28 أغسطس 2026

Some single-page apps capture less text than expected

On sites that render their content in stages after the page has technically finished loading, a save can run before the rest of the article exists in the page, and you get a shorter source than what you were reading. A fix that waits for the content to settle is in progress. In the meantime, scrolling the page to the end before saving reliably captures the whole thing.

What this page is not

There is no uptime probe behind this page, no incident feed, and no percentage. Everything above is a human check on a stated date. A status page that invents numbers is worse than not having one, so the honest version is this: read the changelog to see how quickly things actually get fixed, and email if something is broken for you.

Something broken?

Tell me what you were doing and on which site. It goes straight to the person who can fix it.