ilmzot
Feed your Zotero knowledge into NotebookLM.
ilmzot mirrors Zotero collections into same-named NotebookLM notebooks while
keeping Zotero as the source of truth. It is one-way: local PDFs are uploaded,
but Zotero is never modified and disappeared items are not deleted remotely.
Quickstart
ilmzot setup
ilmzot ls
ilmzot sync "Climate Modelling"
ilmzot status
ilmzot setup detects Zotero at localhost:23119, authenticates NotebookLM
using browser cookies, and creates its local state directory. Use
--browser firefox, --browser "firefox::Work", or --login for interactive
authentication. ilmzot supports major browsers through automatic cookie
detection. An interactive login fallback is available when browser-cookie
extraction is unavailable.
Installation
PyPI and Homebrew releases are coming soon. The intended Homebrew UX is
brew install <user>/tap/ilmzot; it will provide ilmzot directly without
shell configuration. For local development:
git clone <repository-url>
cd ilmzot
uv sync
uv run ilmzot --help
Python 3.10–3.12 is supported (browser-cookie support is most reliable on
3.12). Runtime authentication is provided by notebooklm-py[cookies].
Commands
ilmzot sync --all syncs the personal library to Zotero Library.
-n/--notebook changes the destination name and -d/--dry-run previews work.
ilmzot doctor is diagnostic-only and explains one concrete fix for failures.
Architecture and state
The standard library handles CLI parsing, HTTP, hashing, and state. zotero.py
owns the local Zotero API, notebook.py contains the unofficial NotebookLM
boundary, and state.py stores SHA-256 mappings. State is
$XDG_DATA_HOME/ilmzot/state.json, or ~/.local/share/ilmzot/state.json.
It contains no cookies, tokens, passwords, or browser credentials.
Privacy and limitations
PDFs are read locally from Zotero and uploaded to NotebookLM. No Zotero cloud API key is needed. Group libraries, bidirectional sync, metadata editing, and destructive remote reconciliation are not supported in 0.1.0.
NotebookLM integration relies on an unofficial API exposed through
notebooklm-py and may require updates when Google changes NotebookLM.
ilmzot is not affiliated with Zotero or Google.
Release files for ilmzot 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ilmzot-0.1.0.tar.gz | 21.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ilmzot-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 31.3 kB
Release files / ilmzot-0.1.0.tar.gz
| Download URL | ilmzot-0.1.0.tar.gz |
|---|---|
| Size | 21.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5b9996ed1722ff9e5e412792f6aca954aff747906b6e68840bdef0b6999ecf35
|
|
BLAKE2b-256 checksum How to use checksums |
8263bcfef39ee7e61e8c5f4710d2db66babecae3fd07e9d9bd912e661520bcfe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.
Transparency logRelease files / ilmzot-0.1.0-py3-none-any.whl
| Download URL | ilmzot-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
41268405e38ddb5af93f090cc27e90f0f26a97f46980338b24b40f4f98bc3496
|
|
BLAKE2b-256 checksum How to use checksums |
e2bdbe8284e5869a4b8eadce6fab2aea9c51aea430b39e9b27f696e877152d79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 2, 2026.
Transparency log