#Prerequisite and installation
The CLI declares Node >=20 as an engine requirement. This is advisory: there is no runtime version check.
bash
npm install -g maleta.dev@latest
maleta --version
maleta --helpTo run it once without installing anything, use npx maleta.dev --help. Releases earlier than 0.2 do not include tray.
#Help and commands
text
maleta - local Maleta selection CLI
Usage:
maleta init [--file path]
maleta validate [--file path]
maleta install [--file path] [--tool all|claude|codex|agents] [--dry-run]
maleta sync [--file path] [--tool all|claude|codex|agents] [--dry-run]
maleta lock [--file path] [--dry-run]
maleta tray
maleta --version
Device commands (optional account):
maleta login [--name label] authorize this computer (code at app.maleta.dev/device)
maleta logout revoke the credential and stop following the Maleta
maleta attach <maleta> follow one of your account's Maletas on this computer
maleta detach stop following the bound Maleta
maleta status show what this computer follows and what is pending
maleta watch [--interval seconds] [--once]
apply changes from the bound Maleta (never removes anything)
maleta prune [--dry-run] [--yes] remove only the files this Maleta wrote and no longer needs
maleta tray starts the maleta.dev tray icon in the background. It checks npm at startup and every 24 hours, then restarts after a verified update.
The file targetTool is used when --tool is omitted. targetOs must match the local host.
maleta lock pins every GitHub skill to the commit its ref (or default branch) points at today, so later installs get the same files.
GitHub skills are resolved from the declared public repository/path/ref without executing repository content.
With no arguments, or with --help or -h, the CLI prints this help and exits with code 0. The default file is maleta.json; use --file <path> to specify another path.