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.

Pi Codex App Server 0.2.0

Pi Codex App Server 0.2.0

Source: 535b4caac1d87cc94c449f72fdb28a7b61711a08.

The AdamsGH fork uses the package name @pi-switch/pi-codex-app-server and retains the pi-codex-app-server command, upstream 0.1.2 history, and license notices.

Changes

• Share a native Pi TUI session with Codex through a single-writer owner bridge and subscriber fanout.
• Recover history, active-turn state, and Remote Control relay sequencing across reconnects.
• Deliver completion before idle status and preserve accepted message identities in JSONL receipts.
• Suppress known duplicate submissions before model execution, including persisted-history retries.
• Avoid redundant live-thread announcements that trigger Desktop ownership snapshots.
• Publish only active sessions by default and synchronize recent sidebar order across Windows and WSL.
• Distinguish native Desktop app-tools endpoints from browser transports and rediscover the endpoint after restart.
• Support Pi 1.2.x, show concise Codex model names, and cache unchanged session summaries during startup.
• Include the approved session-sharing demonstration, documentation, and reusable sidebar recovery commands.

Installation

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

Requires Node.js 22.19 or newer and Pi 1.2.x. Windows and Linux CI cover Node 24 and 26. Protocol baseline: Codex CLI 0.162.1. Desktop host tools are private and version-sensitive.

Validation

Local verification passed 192 tests, build, clean package installation, CLI and extension loading, and migration checks. 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 candidate was checked against its recorded source, manifest, and SHA-256, and the packed demonstration GIF matches the approved source asset.

Archive SHA-256: 53d1e46e2c1e2aa176ddf65738433af37b87f1b9f78975575f34fb97f7ee3b7f.

The Pi/Codex CLI demonstration was visually accepted. Manual Windows/WSL Desktop checks covered streaming, tool-error recovery, completion, reconnects, and sidebar behavior. After a full Desktop restart, five sequential WSL submissions passed, including two windows displaying the same chat. Server history confirmed separate completed turns and distinct client message IDs. iOS hardware testing is optional and remains unperformed.

Package behavior

Pi owns model execution, credentials, and JSONL history. Codex approval and sandbox settings do not add a sandbox around Pi. Archiving preserves history; explicit thread deletion removes the Pi session file. No repository skill collection is installed.