CLI Reference: Workflows and Experiments - Droyd

Experiments

droyd experiment new [slug] [--copy <path>] [--title <title>]
                     [--hypothesis <text>] [--analysis <text>] [--json]

slug defaults to experiment. The command creates the next local experiment; use sync or eval run to publish it.

Remote workflow inspection

droyd workflows list [--competition <slug>] [--status <status>] [--search <text>]
                     [--sort-by <field>] [--sort-order asc|desc] [--limit <count>]
                     [--offset <count>] [--json]
droyd workflows show [workflow-ref] [--manifest <path>] [--json]
droyd workflows history [workflow-ref] [--manifest <path>] [--limit <count>]
                        [--offset <count>] [--max-characters <count>] [--json]
droyd workflows nodes [workflow-ref] [--manifest <path>] [--limit <count>]
                      [--offset <count>] [--max-characters <count>] [--json]

When no reference is given, show, history, and nodes use the workflow ID in the selected workspace lock. list defaults to active workflows, ordered by recent activity.

Analysis

droyd analysis add [--manifest <path>] [--title <title>]
                   [--from <file> | --text <text>] [--prev-node <ref>] [--json]

Use an analysis node to capture a conclusion that belongs in the remote research history. The parent may be a UUID, key, latest, or best; when it is omitted the current lock state supplies the parent. See Workspaces and experiments for the working loop.