opschain artifacts list

Included from Basic tier

Lists stored artifacts, newest first, as a table (ID CODE NODE LABELS SIZE CREATED BY); a purged artifact's code is suffixed (purged). -o json|yaml emits the summaries as machine documents.

Locally the per-user store is listed. Against a server the listing reads the node-path index (GET …/artifacts under the node), and the server holds no estate-wide artifact index, so a listing addresses exactly one node — --node is required there.

Flags

Flag	Meaning
--node <path>	Only artifacts stored against this node path (required against a server), e.g. /projects/demo/environments/dev.
--limit <n>	Maximum artifacts to list (default 50).
--filter <column>[!]=<value>	Keep only rows matching the term (repeatable; terms AND). Columns are the printed table headers lowercased (spaces/dashes fold to _); * wildcards match the whole cell case-insensitively, != negates, commas mean any-of. With --filter, the listing is fetched without the server limit, filtered, then --limit truncates the result. Grammar: opschain docs cli.

Exit codes

Code	Meaning
0	Listed (an empty listing is still 0).
1	The store read or server request failed.
2	Usage error.

Named errors

• listing artifacts against a server reads one node's stored artifacts — pass --node <path> (e.g. /projects/demo/environments/dev) — a server target without --node; exits 2.

Examples

opschain artifacts list --node /projects/demo/environments/dev --limit 10

See also

• opschain docs cli/artifacts-get — fetch what a listing shows (the ID column is the exact-id hand-off).
• opschain learn 3.6 — artifacts.