jackwener/OpenCLI · warning · AuthRequiredError

Waiting for Google SSO cookies (SID + SAPISID)

Error message

Waiting for Google SSO cookies (SID + SAPISID)

What it means

During the interactive auth polling loop, each poll first checks for SID and SAPISID cookies; if they have not appeared yet it throws AuthRequiredError 'Waiting for Google SSO cookies (SID + SAPISID)'. This is a transient, expected signal while the user completes Google SSO — polling continues until cookies land and verify() succeeds.

Source

Thrown at clis/notebooklm/auth.js:53

      }
      return { ok: true, name, authuser };
    })()
  `));
  if (probe?.kind === 'auth') throw new AuthRequiredError(NOTEBOOKLM_DOMAIN, probe.detail);
  if (!probe?.ok) throw new CommandExecutionError(`Unexpected NotebookLM probe: ${JSON.stringify(probe)}`);
  return { name: probe.name, authuser: probe.authuser };
}

registerSiteAuthCommands({
  site: 'notebooklm',
  domain: 'google.com',
  loginUrl: `https://accounts.google.com/ServiceLogin?service=lso&continue=${encodeURIComponent(NOTEBOOKLM_HOME_URL)}`,
  columns: ['name', 'authuser'],
  quickCheck: hasNotebookLmSsoCookies,
  verify: verifyNotebookLmIdentity,
  poll: async (page) => {
    if (!await hasNotebookLmSsoCookies(page)) {
      throw new AuthRequiredError(NOTEBOOKLM_DOMAIN, 'Waiting for Google SSO cookies (SID + SAPISID)');
    }
    return verifyNotebookLmIdentity(page);
  },
});

View on GitHub (pinned to 49907e53dc)

Solutions

1. Complete the Google sign-in in the opened browser window, including 2FA.
2. Keep the login tab open until redirected back to NotebookLM.
3. If polling times out repeatedly, restart login with a profile that already has a Google session.
4. Check that popups aren't blocked, preventing the accounts.google.com flow.

await pollUntil(async () => {
  try {
    return await quickCheck();
  } catch (e) {
    if (String(e.message).includes('Waiting for Google SSO cookies')) return null; // keep waiting
    throw e;
  }
}, { timeoutMs: 120000, intervalMs: 2000 });

When it happens

Trigger: Polling fires while the user is still on the Google login page (has not finished sign-in), or the login tab was closed/abandoned so cookies never get set.

Common situations: User slow to complete 2FA; user closed the login window; Google blocked the automated browser; wrong login URL opened.

Related errors

• Waiting for Bilibili session cookies
• Waiting for Douban dbcl2 / ck cookies
• Waiting for GitHub session cookies
• huggingface.co
• Waiting for Jike login: ${detail}

AI-assisted analysis of jackwener/OpenCLI@49907e53dc (2026-08-29). Data as JSON: /api/errors/e9fdd3a3f55b3314. Report an issue: GitHub.