Troubleshooting¶

Even with a correct configuration, problems can occur. This chapter collects the most common situations and their solutions.

Authentication problems¶

Authentication doesn't start automatically

If a request to NotebookLM fails without opening the login window, check the server status:

Check NotebookLM status

Claude uses the get_health tool to diagnose the problem. Based on the result, it may be sufficient to manually start authentication with setup_auth.

Persistent authentication problems

In case of repeated errors, the most effective solution is a complete cleanup followed by a new authentication:

1. Ask Claude: Run NotebookLM cleanup preserving the library
2. Verify the preview of what will be deleted
3. Confirm the operation
4. Re-authenticate: Set up authentication for NotebookLM

The cleanup removes browser data, cache, and corrupted profiles, while preserving the registered notebook library.

Response problems¶

Responses contain external knowledge

If responses seem to integrate information not present in the documents: 1. Verify that the system is actually using the ask_question tool (automatic structuring is only active with this tool) 2. Try rephrasing the question more specifically 3. Verify on NotebookLM that the structured prompt was actually sent, by checking the chat history in the notebook 4. Verify that the ask_question tool actually returned a response. In Claude Desktop's chat, expand the tool call detail and check that the Response field contains NotebookLM's text. If the response is absent or contains an error, Claude may have generated the response autonomously with its own knowledge.

Timeout or no response

NotebookLM can time out if the prompt contains problematic formatting. The system automatically handles this by avoiding decorative lines in prompts, but if the server source code has been customized, verify that no sequences of === or --- are present at the beginning of the structured request sent.

Missing citations in the response

Very generic questions can produce less structured responses. Rephrasing with greater specificity improves citation quality. For example, instead of "Tell me about the project", ask "What are the project milestones and their deadlines, with reference to the documents?".

Unexpected [NOT FOUND IN DOCUMENTS]

This declaration is correct behavior — it means the sought information is not in the uploaded documents. Verify that the selected notebook is the right one and that the relevant documents are actually present in NotebookLM.

Connection problems¶

Error "browserContext.newPage: Target page/context/browser has been closed"

The server recovers automatically from this error by recreating the browser context. Simply retry the request.

"ProcessSingleton" error or profile conflicts

The server is configured to automatically handle this situation using isolated browser profiles. If the problem persists, verify that there are no residual server processes and retry.

Account limits¶

Daily limit reached

Free accounts have a limit of 50 queries per day to NotebookLM. The counter resets at midnight (UTC time). Available options:

• wait for the counter to reset
• use the re_auth tool to switch to a different Google account (if you have multiple accounts)
• consider a NotebookLM Plus subscription for higher limits (500 queries per day)

Complete cleanup¶

If problems persist despite troubleshooting attempts, you can perform a deep cleanup that removes all server data while keeping the notebook library:

Run complete NotebookLM cleanup preserving the library

The cleanup scans eight categories of files: current installation data, NPM cache, server logs, temporary files, and other residual data. Before deleting anything, the system shows a detailed preview of what will be removed and waits for explicit confirmation. After cleanup, re-authentication is required.