vitrinkaDocsBack to the vitrína

Command reference

The full top-level surface. Every command takes --base to point at a deployment and --json to emit machine-readable output on stdout.

Working surfaces

CommandWhat it does
boardAnnotation boards.
setScreenshot and artifact sets.
artifactSelf-contained interactive pages.
diagramRefreshable architecture diagrams.
workThe annotation work queue.
tagThe tag vocabulary — the third axis beside project and subgroup.

Session and machine

CommandWhat it does
statusSession dashboard: live board, open work queue, and listener lease.
openOpen the thing you're working on — the set's live board, or vitrinka home.
uiOpen the dashboard. Running vitrinka bare on a terminal does the same.
editOpen a file or project in the Vitrinka editor.
configThis machine's vitrinka settings.
authCredentials, one per deployment.
projectThis repository's vitrinka wiring.
tidySweep legacy roots and stray shots into .vitrinka/.

Setup and administration

CommandWhat it does
install / uninstall / updateOnboard, remove, or refresh every installed surface.
doctorCheck this machine's setup and name the repair for each failure.
extensionInstall, update and diagnose the recorder extension.
adminDeployment administration — currently the mailer (admin smtp).
completionGenerate the shell autocompletion script.
aiAsk for a vitrinka command in plain words.

Publishing without the CLI

Nothing about publishing requires the CLI. A tar pipe publishes a whole set from any job you already run — no SDK to install, nothing to keep up to date in the pipeline.

tar czf - ./shots | curl -sS -X POST \
  -H "Authorization: Bearer $VITRINKA_TOKEN" \
  --data-binary @- "$VITRINKA_URL/api/v1/sets?name=nightly"

MAX_SET_MB (default 200) caps both the request body and the unpacked size of a single set.