Clyde Help

sync

Upload scanned repository chunks to NotebookLM after explicit approval.

AccessUploads repository chunks
NetworkNotebookLM backend
SourceBuilt-in Clyde command

Syntax#

clyde sync REPO --notebook-id ID --approve-upload [scan flags]

Options#

FlagPurpose
--notebook-idNotebookLM notebook id.
--notebook-urlNotebookLM notebook URL.
--approve-uploadRequired explicit upload approval.
--backendNotebookLM backend: mcp or nlm.
--mcp-commandCommand used for MCP backend.
--nlm-commandCommand used for nlm backend.
--delete-existing-sourcesWith --backend nlm, delete all existing notebook sources first.
--mcp-timeoutSeconds to wait for each backend response.
--status-urlOptional Clyde daemon JSON-RPC URL.
--dry-runPlan the selected sync without uploading or deleting sources.
--receiptPath for the local sync receipt.
--resumeResume an eligible receipt after checking its bundle.
--heartbeat-intervalSeconds between simple status updates during backend work.
--quiet-progressSuppress real-time progress lines.
--job-idStatus daemon job id.
--subjectGenerate a dated NotebookLM book title.
--book-titleUse an exact NotebookLM book title.
--includeOnly include matching globs; repeatable.
--excludeSkip matching globs in addition to defaults; repeatable.
--exclude-folderSkip a folder and its descendants; repeatable.
--max-file-bytesSkip files larger than this many bytes.
--max-chunk-charsSplit source text at this many characters.

Arguments#

  • REPO

Examples#

clyde sync --bundle .clyde/out --notebook-id "your-notebook-id" --dry-run
clyde sync . --notebook-id "your-notebook-id" --approve-upload
clyde sync . --notebook-id nb --approve-upload --backend nlm
clyde sync . --notebook-id nb --approve-upload --status-url http://127.0.0.1:5876/rpc --job-id clyde-sync

Example Use Cases#

Build a reviewed bundle, run sync --dry-run, then approve the exact bundle digest. Use receipt status to inspect a local receipt before resuming an interrupted sync.

Safety Notes#

Clyde is a local workflow harness, not an operating-system sandbox. Review bundles before upload, keep NotebookLM notebooks private, and avoid sending secrets, customer data, production records, tokens, credentials, browser state, or private keys.