Tools and their versions

The local runner is the engine; the tools it runs are installed on their own, the way Docker Desktop lists images next to the engine that runs them.

The Tools list

Open it from the runner's flyout in the status bar (Manage tools…) or the command palette (Manage tools on the runner…). Each tool shows:

the versions on this computer, with their size on disk and when each last ran;
the newest version the registry knows, and Update to … when it is not installed yet;
Install for any listed version, Remove for one you no longer need;
Runs: which version a run of this tool uses. By default the newest; choose an older one to repeat an analysis exactly as it was. The choice is kept in this browser.

A tool you never installed installs itself on its first run, as before.

Versions arrive without a new runner

What versions exist is a list on this site, /runner/tools.json: for each version, where it comes from (a git commit, a package version, or a container image by its digest). The runner ships with the list as it was at its release and fetches the current one when it starts and when you press Check for new versions. A new MuSiCal or MuTopia is a line in that list, not a runner release.

Versions install side by side, each in its own folder (~/.cache/sigscape-daemon/tools/<tool>/v/<version>), so installing one never changes another.

Every run names its version

A run records the tool version it used: on its row under the Run button (k 2–8 · 20 replicates · 2b0c246) and in its recipe.json (toolVersion, with the exact source). MuTopia is pinned by its image digest, not latest, so a result can always be traced to the image that made it.

For agents and scripts

GET /api/registry: every tool, its versions, which are installed, size and last run.
POST /api/registry/<tool>/<version>: install one; returns a job to follow like any run.
DELETE /api/registry/<tool>/<version>: remove one (refused while that tool runs).
POST /api/registry/refresh: fetch the current list from the site.
A run asks for a version with the parameter tool_version.

The Tools list

Open it from the runner's flyout in the status bar (Manage tools…) or the command palette (Manage tools on the runner…). Each tool shows:

the versions on this computer, with their size on disk and when each last ran;

the newest version the registry knows, and Update to … when it is not installed yet;

Install for any listed version, Remove for one you no longer need;

Runs: which version a run of this tool uses. By default the newest; choose an older one to repeat an analysis exactly as it was. The choice is kept in this browser.

A tool you never installed installs itself on its first run, as before.

Versions arrive without a new runner

Versions install side by side, each in its own folder (~/.cache/sigscape-daemon/tools/<tool>/v/<version>), so installing one never changes another.

For agents and scripts

GET /api/registry: every tool, its versions, which are installed, size and last run.

POST /api/registry/<tool>/<version>: install one; returns a job to follow like any run.

DELETE /api/registry/<tool>/<version>: remove one (refused while that tool runs).

POST /api/registry/refresh: fetch the current list from the site.

A run asks for a version with the parameter tool_version.