v0.2.0 — Pi 1.0 and tool settings

Pix v0.2.0 adds Pi 1.0 support, global tool selection, and built-in agent features.

What's new

• Settings → Tools: choose the tools offered to the model, enable all, or disable all. New sessions default to all selectable tools, including codemode and tool_search. Explicit saved choices are retained. Changes can also apply to the current connected session.
• Pi 1.0 support: native MCP, codemode and tool search integration; explicit input-handling results; nested tool-call summaries; and consistent context usage after context edits and compaction.
• Built-in agent features: subagents, task lists, structured questions, and side chat, with settings controls and runtime activity views. Subagent notifications arrive at tool boundaries and avoid duplicate results.
• Session reliability: fast commands that finish without a model response no longer leave the server or input box marked busy. Terminal snapshots reach the correct session, and blocked writes still respect their deadlines.
• UI improvements: stable session ordering, clearer running activity, and working task-list expansion controls.

Install

Requires Node.js 22.19.0 or newer.

npm install --global @fffattiger/pix-cli@0.2.0
pix start

The npm package includes the CLI, web client, runtime packages, Pi's coding-agent SDK, and the patched subagent plugin. npm installs their external dependencies normally. A version-limited packaging fix excludes the defective Pi SDK 1.0.0 shrinkwrap; SDK code is unchanged. The attached standalone archive includes the full dependency closure for offline installation.

Upgrade from 0.1.x

The runtime build contracts have changed. Let active tasks finish, then stop the old daemon with its authenticated CLI command before installing the update:

pix down --all
npm install --global @fffattiger/pix-cli@0.2.0
pix start

Keep the existing session and configuration directories. Session history remains in JSONL files; no database migration is required. The Tools picker controls tools exposed directly to the model; MCP server availability remains a separate setting.

Validation

The feature baseline passed 3,519 tests, with one platform-specific skip, plus architecture checks, type checks, build, package boundaries, command coverage, and startup/runtime/session end-to-end tests. Independent reviews covered the new tool preferences, save/apply ordering, fast-command completion, and release packaging.

Release checks also verified workspace/dependency versions, build identities, offline installation of the standalone archive, a real daemon session round-trip, authenticated shutdown, and exact session/message retention after an upgrade simulation. Uninstalling the CLI preserved that session data. Temporary disk exhaustion interrupted the first upgrade run; the same standalone artifacts passed the remaining checks after space was freed. The npm distribution is separately checked with a fresh registry install, including the bundled plugin, default tools, web startup, and session lifecycle.