sync-notebooklm-kb

You can sync local Obsidian articles to a NotebookLM knowledge base by running a synchronization script that classifies, compares, and updates notebook sources. It strictly matches local Markdown files to add only new articles and prevent duplicates.

The best way to keep a local article directory aligned with NotebookLM sources is an automated synchronization workflow. It reduces manual maintenance and drift by strictly comparing local Markdown files against the notebook to push only new articles.

Yes, you need Git and Python to automate NotebookLM knowledge base updates. The synchronization workflow requires Python to run the markdown_converter classification script, Git to manage article repositories, and the NotebookLM CLI to update sources.

Yes, you can use a remote VPS to clone and sync articles with NotebookLM. The synchronization workflow supports remote VPS setups that clone the article repository and update NotebookLM sources directly without requiring a local Obsidian environment.

Your NotebookLM sync script adds duplicate sources if it lacks strict matching between local Markdown files and existing notebook sources. The synchronization workflow performs strict matching to ensure it adds only new articles to the knowledge base and avoid duplicates.