Skip to content

yasp-toolkit install

Add yasp-agent extras and other yasp packages from the yasp registry to the environment yasp-toolkit runs from. The registry key is minted from your production login on each run; it never lands on the command line or in pipx or uv metadata.

Usage:

$ yasp-toolkit install [OPTIONS] [extras]...
Argument Default Description
extras... — yasp-agent extras to add, e.g. gaia, kronos-edge; core comes with any.
Option Default Description
-p, --package <str> — Another package to add, as a pip requirement. Repeatable.
-U, --upgrade — Upgrade yasp-agent, every installed yasp package and all their dependencies.
-g, --global — Allow changing a system interpreter or a pipx --global environment.
--torch <str> — PyTorch build: cpu, cu128, rocm6.4, xpu, ..., or default for PyPI's. Default: the installed torch's, else the remembered one, else cpu. Remembered.
yasp-toolkit install gaia kronos-edge
yasp-toolkit install -p yasp-gaia-toolkit
yasp-toolkit install -U
Extra Adds
gaia eval, kernelgen, who-am-i
kronos-edge embedded, dataset
core activity; installed with any other extra

Environments

yasp-toolkit runs from Install -U
pip venv python -m pip install --upgrade --upgrade-strategy eager
uv venv uv pip install --upgrade
pipx pipx inject pipx upgrade --include-injected
uv tool uv tool install, keeping the tool's requirements --upgrade
system interpreter python -m pip install, --user for a user-site install; needs -g as pip venv
pipx --global as pipx, with --global; needs -g as pipx
  • In a venv, -U upgrades yasp-agent, its installed extras, every installed yasp-* package and all their dependencies.
  • Editable and URL installs stay installed as they are, -U or not: pip, uv and pipx get them as name==<installed version> constraints (PIP_CONSTRAINT, UV_CONSTRAINT), so a package needing another version fails to resolve instead of replacing them. A uv tool's editables are reinstalled with --editable / --with-editable.
  • In a pipx or uv tool environment, -U upgrades the whole environment.
  • Setup per installer: pipx, uv.

Package index

YASP_PACKAGE_INDEX replaces the yasp registry with another simple-index URL, e.g. a mirror:

export YASP_PACKAGE_INDEX=https://mirror.example/simple/
  • No registry key is minted or sent, so no login is needed. Credentials, if the index needs any, go in the URL: https://user:password@mirror.example/simple/.
  • A plain-http index is added to PIP_TRUSTED_HOST for pip.

PyTorch build

torch comes with the gaia and kronos-edge extras, from the PyTorch index of one build:

  1. --torch;
  2. else the installed torch's build (2.9.1+cu128 → cu128; no label → default);
  3. else the one remembered in ~/.config/yasp/install.json;
  4. else cpu.

The build used is remembered for later installs. default is PyPI's own build. uv venvs and uv tools take it as --torch-backend, pip and pipx as an extra index (https://download.pytorch.org/whl/<build>).

--torch picks the build, -p torch==<version> the version:

yasp-toolkit install kronos-edge --torch cu128 -p 'torch==2.9.1'

--torch does not replace a torch that is already installed; uninstall it first to switch builds.