Repository navigation
v0.2.1 — Static settings and clickable tools
Pix v0.2.1 makes global settings usable without a selected project or active session, and fixes several runtime and navigation issues.
Changes
- Clickable tool switches: Settings → Tools shows 16 common tools and additional saved tool names as switches. Keep all tools enabled, disable all, or save a custom selection. Unknown saved names are preserved; conflicts and failed saves keep your edits.
- Static global settings: settings read persisted configuration and global on-disk catalogs. Browsing does not activate a worker, execute extensions or package-manager commands, or discover models over the network. Saved tool defaults take effect when a session next starts or loads.
- Images and questions: preserve image content in runtime messages, support native multi-question forms, and retain questionnaire drafts while activity updates arrive.
- Runtime activity: show pending and accepted turns as busy until authoritative completion, and keep existing live sessions observable while child agents run. Browsing inactive history starts no worker.
- New-session navigation: open a new-session draft from a session link even when no project is selected. Choose the project before sending.
Install or upgrade
Requires Node.js 22.19.0 or newer.
npm install --global @fffattiger/pix-cli@0.2.1
pix startWhen upgrading a running installation, let active tasks finish and stop the old daemon before replacing the CLI:
pix down --all
npm install --global @fffattiger/pix-cli@0.2.1
pix startKeep your existing session and configuration directories. History remains in JSONL files; no database migration is required. Settings change persisted defaults and leave existing sessions' choices in place until they next start or load.
The regular .tgz is the npm distribution; npm installs its external dependencies. The -standalone.tgz archive contains the dependency closure for offline installation. SHA256SUMS covers both archives.
Validation
The release passed 3,662 tests with one Windows-only skip, architecture and type checks, build, package boundaries, command coverage, and startup/runtime/session end-to-end tests. The standalone archive passed offline installation, a real daemon session round-trip, authenticated shutdown, history browsing with zero workers, an upgrade simulation, and uninstall preserving session data.
Independent installation checks also passed a fresh npm-package install and an actual 0.2.0 → 0.2.1 upgrade. The upgraded installation retained the exact session identity, messages, and JSONL bytes; history reads started zero workers, and uninstall preserved the session and configuration files.