Pi Codex App Server 0.2.1

Pi Codex App Server 0.2.1

Opening an active session in another native Pi window with pi -c previously exited that window when the extension could not acquire the app-server session lease.

Fixes

• Keep native Pi and its input usable when app-server attachment fails. Show codex: disconnected (session in use) when another window holds the lease.
• Show codex: connected in the attached window instead of the daemon label and WebSocket URL. Connection details remain in /codex-server status.
• Prevent daemon commands from overwriting a disconnected window's attachment status.
• Exclude local acceptance reports from Git and npm packages.

Validation

Local verification passed 195 tests, build, clean npm installation, CLI and extension loading, and migrations. The user confirmed that native pi -c stayed open, reloading the original window succeeded, and the two panes showed connected and disconnected respectively.

The release preparation workflow passed all nine jobs, including installation of the same archive on Windows and Linux with Node 24 and 26. The downloaded archive matches its source commit, manifest, and SHA-256.

The archive downloaded from npm after publication matches the CI archive. Its clean installation, CLI and extension loading, and migration checks passed.

Installation and limits

pi install npm:@pi-switch/pi-codex-app-server@0.2.1

The declared requirements remain Node.js 22.19 or newer and Pi 1.2.x. No launcher or Pi runtime changes are required.

The app-server lease remains exclusive. Disconnected native Pi windows are outside its history-write coordination; this release does not establish safe concurrent native JSONL writes. Desktop and Remote Control acceptance were not repeated for this patch, and the previously investigated Desktop ownership uncertainty is unchanged.

Source: c8759b1d9086ddaa6ea280334ecc2d412bec490e.

Archive SHA-256: 9621fd248eace84082b2bb723d0f3121e766f013075189cea241345e640b87b8.