lb add
Synopsis
Section titled “Synopsis”lb add <title> [options]Description
Section titled “Description”lb add creates a node directly from text content, bypassing the capture pipeline. It is useful for adding written notes, observations, or structured content that does not have a source URL.
Body content can be provided inline with --body, read from a file with --body-file, or piped from stdin. --body and --body-file are mutually exclusive.
Arguments
Section titled “Arguments”| Argument | Description |
|---|---|
title | Required. The title of the node. |
Options
Section titled “Options”| Option | Type | Description |
|---|---|---|
--body <text> | string | Inline body content. Mutually exclusive with --body-file. |
--body-file <path> | string | Path to a file containing body content. Max 5 MB. Mutually exclusive with --body. |
--summary <text> | string | Short summary of the node. |
--tags <tags> | string | Comma-separated PARA item IDs to tag the node with. |
--para <id> | string | Single PARA item ID shorthand for tagging. |
--why <text> | string | Why you are adding this node. Used for ranking and recall. |
--json | flag | Output raw JSON. |
--api-url <url> | string | Override the API base URL. |
Examples
Section titled “Examples”Add a short note with inline body:
lb add "Rate limiter options" --body "Token bucket vs leaky bucket — prefer token bucket for burst tolerance." --why "architecture decision"Add a node from a markdown file:
lb add "Q4 Research Notes" --body-file ./notes/q4.md --why "reference"Pipe body from stdin (macOS example — use xclip -o on Linux):
pbpaste | lb add "Copied snippet" --why "save for later"Tag with a PARA item on creation:
lb add "Auth spike findings" --para proj_abc123 --why "design input"Output the created node as JSON:
lb add "Quick note" --body "Remember to check the DB index." --why "ops" --json | jq '.id'