CLI Configuration

Global config

The CLI reads global configuration from:

~/.config/notebind/config.toml

Fields

api_url = "https://notebind.com"
api_key = "nb_sk_a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6"

Field	Default	Description
api_url	https://notebind.com	API base URL
api_key	-	Your API key (set via notebind auth)

Project manifest

Each project has a .notebind/manifest.toml file created by notebind init:

[documents]
"article.md" = "6240800a-1234-5678-abcd-ef0123456789"
"guide.md" = "7351911b-2345-6789-bcde-f01234567890"

The [documents] table maps local file paths (relative to project root) to remote document IDs.

Mapping behavior

• notebind push file.md checks the manifest for an existing mapping
  • If mapped: updates the remote document
  • If not mapped: creates a new document and adds the mapping
• notebind link file.md DOC_ID manually adds a mapping
• The manifest is a plain TOML file — you can edit it manually

Directory structure

your-project/
├── .notebind/
│   └── manifest.toml      # File-to-document mappings
├── article.md              # Your markdown files
└── guide.md

Self-hosted instances

To point the CLI at a self-hosted Notebind instance, set api_url in the global config:

api_url = "https://notebind.yourcompany.com"
api_key = "nb_sk_..."

Or set it via environment variable (overrides config file):

NOTEBIND_API_URL=https://notebind.yourcompany.com notebind list