notebooklm-upstream-auth-fingerprint-rejection
Migrating cookies from notebooklm-py’s storage_state.json to upstream notebooklm-mcp-cli’s profiles/default/cookies.json format does not produce working auth. Google enforces HTTP client fingerprinting — cookies captured by notebooklm-py’s client are rejected when replayed via the upstream’s httpx-based client. Fresh cookies must be captured from a live browser session using the upstream’s own nlm login flow (Chrome CDP).
Related
- notebooklm-mcp-cli-auth-requires-fresh-capture-not-migration
- notebooklm-py-cookies-rejected-by-upstream-client-fingerprin
- notebooklm-cookie-refresh-cron-must-update-on-migration
- notebooklm-mcp-cli-auth-format-two-files
- notebooklm-mcp-cli-auth-two-file-format
- notebooklm-upstream-auth-google-fingerprint-rejection
- notebooklm-upstream-auth-two-file-format
- notebooklm-upstream-auth-requires-fresh-cookies-not-migrated
- notebooklm-legacy-cookie-refresh-cron-obsolete-after-upgrade
- notebooklm-mcp-cli-rejects-migrated-notebooklm-py-cookies
- xint-bun-runtime-not-node