Skip to main content
A short reference for the words this documentation uses. Canvas-related terms include the same color you see in the app.

Workspace

A saved NodePad canvas. A workspace holds branches, text notes, references, merge sources, and a default model. Each workspace has its own URL.

Canvas

The 2D surface that holds a workspace’s branches, text notes, attachments, and edges. You pan and zoom across the canvas instead of scrolling a single transcript.

Branch

A conversation path through the canvas. A branch is a chain of nodes connected by edges. Most workspaces have several branches that diverge at chosen messages.

Node

A single message on the canvas: a user message, an assistant reply, or an in-progress draft. Nodes are the units you fork, edit, re-run, reference, and merge.

Text note

A freeform note pinned to the canvas. Text notes are for human context — research questions, decision logs, checklists. They do not act as persistent prompt constraints.

Reference

A targeted cross-link from one node to another, created with @. References travel with the message that owns them. Visually a on the canvas.

Merge sources

A set of nodes selected as source context for a new draft. Merging combines messages from different branches into one new message. Visually a on the canvas.

Edge

The visible line between two nodes on the canvas. Edges carry meaning: a moves the conversation forward, a branches off a new path, a pulls several sources into one draft, and a cross-links one message into another.

Attachment

A file or image attached to a message. Attachments stay with the node that used them and travel into branches and merged drafts so the receiving model has the same context.

Workspace instructions

Workspace-level prompting and guidance. Applies to every send in the workspace unless overridden.

Default model

The model NodePad picks when you start a new branch in this workspace. You can override it for any individual send.

Bring your own keys (BYOK)

Connecting your own provider API keys so NodePad routes model requests through your account. Useful when usage, rate limits, or billing should stay on your provider relationship.

Posture (enterprise)

The deployment shape: connected to the internet, proxied through a mirror, fully air-gapped, or a single-VM trial. See installing NodePad for the matrix.