Glob
Log in
Menu
Skip to the guide

Command reference

Views, pins and projects

Switch your current view, create notes or tasks there, pin records and turn a branch into a project.

The node commands organise notes and tasks into a current view. Use them when you want a new item to belong inside a particular container, or when you want a pinned record to be easy to find.

These commands require the Linux store. They appear in macOS command help, but the macOS CLI cannot open the kind of store they require and reports This command requires a package-backed Glob store. Basic notes and tasks remain available there.

Every command on this page accepts --store <directory>, --json and --help. They use the same selected store as the other CLI record commands. IDs must be complete UUIDs. Replace "$node_id" and "$container_id" in the examples with your own IDs.

List the current view

glob list
glob list --tasks --json

glob list shows the current note list. Add --tasks to show the task list. Unlike glob notes list, this follows the selected view:

  • At the root, it lists eligible notes or tasks in your inbox or task list, including explicitly sent references.
  • Inside a container, it selects visible records of the requested type belonging to that container.

The JSON result contains view and records. view contains kind (root or container), label, and container_id when a container is selected. records is an array of the standard record summaries.

There is no --limit or --all option on glob list. Do not assume it has the filtering or creation-time order of notes list or tasks list.

Switch views

glob switch "$container_id"
glob list
glob switch --root

glob switch <id> saves the selected container for subsequent commands. The choice remains after the command exits. glob switch --root returns to the root inbox and task list.

Supply exactly one of an ID or --root. Supplying neither or both fails with provide either a container id or --root. A validly formed ID that does not exist fails with NOT_FOUND.

Switching does not move any records. It changes where glob list looks and where glob new creates. The JSON result is { "view": { … } }.

Create in the current view

glob new "Packing ideas"
glob new "Buy a travel adapter" --task

glob new <title> creates a note in the selected view. --task creates a task instead. At the root, the new item belongs to the root list. Inside a container, it belongs to that container. The result is a record summary.

Use glob notes new --title … --body … --tag … when you need body text or tags at creation. That record command does not use the selected node view. You can edit the body or tags of a node you have just created with glob notes edit <id>.

Pin records

glob pin "$node_id"
glob pinned --json
glob unpin "$node_id"

glob pin <id> adds an ID to your pins. glob unpin <id> removes it. glob pinned returns the pinned records that are available in the selected store.

Pinning is a reference, so it does not copy the record. pin and unpin return { "id": "…", "pinned": "true" } or "false"; these values are strings. pinned returns { "records": [ … ] }.

The pin command validates the UUID's shape but does not check that the record exists. A missing record can therefore be accepted by pin and still be absent from pinned. Check it with glob notes show <id> if a pin does not appear.

Make a project

glob project "$node_id" --title "Summer trip" --json

glob project <id> --title <text> promotes a node into a new project container. The title is required. A node in the root inbox moves into the new container. A node with a branch in the selected container takes that branch with it.

The JSON result contains:

Field Meaning
container_id The new project's ID.
moved_record_ids Records moved into the project.
placed_record_ids Records placed as part of the operation.

Use the returned container_id with glob switch <id> to work inside it. Promotion does not itself switch your current view. If a node appears in several places, select the intended source container first so the command can determine which branch to promote.

Failures and boundaries

Malformed IDs produce INVALID_ARGUMENT with exit 2. Missing nodes produce NOT_FOUND with exit 1. TOPOLOGY_CHANGED means the branch changed while an operation was checking it; inspect the current view before trying again. STORE_UNAVAILABLE means the selected store cannot provide this feature or could not be opened.

The command line has no registered commands for sending or removing list references, copying a branch, removing a project listing or deleting a whole container. Use the commands above only as shown in glob --help.

The TUI exposes several of these actions through its Pinned and Node views. For moving data outside Glob, read Markdown export and import.