Main
Treat auth as a first-class step: run
notebooklm auth check --testafter login, and keep a known-good storage state for CI/headless usage.Start with a small notebook + 1–2 sources, then add
generate/downloadflows only after you can reliablyaskwith citations.Because this is an unofficial wrapper over undocumented APIs, pin versions in automation and expect breakage; keep troubleshooting links near your runbooks.
Source-backed notes
- README explicitly warns it is unofficial and uses undocumented Google APIs that may break without notice.
- README shows CLI flows: create/use notebooks, add sources, ask questions, generate artifacts, and download outputs (MP3/MP4/PDF/PNG/CSV/JSON/Markdown).
- README notes a browser-based login via Playwright Chromium and includes a size/time hint for the Chromium install (~170MB; ~30–90s).
FAQ
- Is this affiliated with Google?: No — README says it’s unofficial and not affiliated with Google.
- Can I use it headless?: Yes — README documents cookie/storage-state based auth paths, but you should validate with
auth check. - What breaks most often?: Auth and internal endpoints; pin versions and keep troubleshooting docs handy.