notebooklm-mcp-cli-auth-requires-fresh-capture-not-migration
Migrating cookies from notebooklm-py’s storage_state.json to upstream’s profiles/default/cookies.json produces valid format but Google rejects the session. The upstream client uses different HTTP headers/fingerprint than notebooklm-py, so Google enforces a fingerprint check that invalidates migrated cookies even when they aren’t expired. Fresh cookies must be captured through the upstream’s own nlm login auth flow (Chrome CDP), not transplanted from the old library.
Related
- notebooklm-py-cookies-rejected-by-upstream-client-fingerprin
- notebooklm-mcp-cli-auth-format-two-files
- notebooklm-cookie-refresh-cron-must-update-on-migration
- notebooklm-mcp-cli-auth-two-file-format
- notebooklm-mcp-cli-auth-two-file-profile-format
- notebooklm-upstream-auth-fingerprint-rejection
- notebooklm-upstream-auth-google-fingerprint-rejection
- notebooklm-upstream-auth-requires-fresh-cookies-not-migrated
- chrome-devtools-console-paste-protection-requires-allow-past
- notebooklm-legacy-cookie-refresh-cron-obsolete-after-upgrade
- notebooklm-mcp-cli-rejects-migrated-notebooklm-py-cookies
- google-auth-cookies-httponly-use-network-tab-for-extraction
- notebooklm-legacy-cookies-rejected-by-upstream-client
- browser-httponly-cookies-not-accessible-via-document-cookie
- notebooklm-migrated-cookies-rejected-different-http-fingerpr
- notebooklm-py-cookies-rejected-by-upstream-client
- nlm-login-manual-file-accepts-cookies-json-format
- notebooklm-auth-fingerprint-mismatch
- notebooklm-upstream-auth-http-fingerprint-rejects-migrated-c
- xint-data-dir-writes-to-release-internal-by-default