Skip to content

List baselines

Baseline files of the workspace, with name, date, view and number of elements (ADR-0018).

Command baseline.list. Reads the workspace and changes no file.

No input.

Field Type Required Description
baselines array of object yes The valid baselines, in file order (code units of the file name).
baselines[].name string yes
baselines[].file string yes Relative to the workspace root, / as separator.
baselines[].repository string yes The repository that holds the file.
baselines[].date dateTime yes A date and time with time zone (RFC 3339 date-time), for example 2026-10-26T09:30:00Z.
baselines[].view viewId no The variant whose baseline it is: its stored selection is only that view (SR-103 AK4). Left out otherwise.
baselines[].elements integer yes Number of elements in the file.
location location yes The baselines folder: the workspace file’s baselines, or baselines in the main repository.
problems array of problem no baseline.invalid of the files that are no valid baseline.
incomplete incomplete no The repository of the baselines folder is not here, so its baselines are not seen (SR-006 AK2).

In the command prompt (Ctrl+Shift+P, macOS ⌘⇧P): the command List baselines.

reqseq baseline list, with --json for the output as JSON. Its help:

Usage: reqseq baseline list [options]
Baseline files of the workspace, with name, date, view and number of elements
(ADR-0018).
Options:
--input <json|@file|-> command input as JSON: inline, from a file, or from
standard input
--workspace <path> workspace root (default: nearest folder upwards with
reqseq-workspace.yaml)
--json print exactly the command output as JSON
--yaml print the whole command output as YAML, problems one
per line
-h, --help show help

POST /v1/commands/baseline.list on the local API (reqseq serve api), with the input as the JSON body; the answer is the output.

Tool baseline_list of the MCP server (reqseq mcp), with the input as its arguments.