ysa runtime
Manage sandbox runtimes (via mise) for the current project. Changes are persisted to .ysa.toml.
Usage
ysa runtime <action> [tool] [options]| Action | Description |
|---|---|
add <tool@version> | Add a runtime to the sandbox |
remove <tool> | Remove a runtime |
list | Show all configured runtimes and packages |
detect | Auto-detect runtimes from the project and write to .ysa.toml |
Options
| Flag | Type | Default | Description |
|---|---|---|---|
-p, --project <path> | string | auto-detected git root | Project root directory |
Examples
Add Node.js 22:
bash
ysa runtime add node@22Auto-detect from the project (reads package.json, pyproject.toml, go.mod, etc.):
bash
ysa runtime detectList what's configured:
bash
ysa runtime listRemove a runtime:
bash
ysa runtime remove nodeNotes
- Runtimes are installed inside the container at task start using mise. They are not installed on your host.
- The
.ysa.tomlfile should be committed to the repo so all team members use the same sandbox runtimes. - Apt packages can also be added via
.ysa.tomldirectly — see the Runtimes guide.
Related
- Runtimes guide — full
.ysa.tomlreference ysa setup— first-run setup