pi-openai-codex-compat 0.0.19 → 0.0.20

package/CHANGELOG.md

@@ -2,6 +2,18 @@
 
 ## Unreleased
 
+## 0.0.20 - 2026-10-02
+
+### Fixed
+
+- Omit incompatible response-item IDs when replaying grammar-tool calls that came
+  from another provider or were recorded as function calls.
+  Call/result pairing and valid same-model item IDs remain unchanged.
+
+### Changed
+
+- Require Pi `>=1.0.0 <1.1.0`. Restart Pi after upgrading its runtime.
+
 ## 0.0.19 - 2026-10-01
 
 ### Removed

package/README.md

@@ -22,18 +22,20 @@ Pi provides the Codex OAuth flow and model catalog. At session start, this packa
 ## Requirements
 
 - Node.js 22.19 or newer
-- Pi `>=0.99.1 <0.100.0`
+- Pi `>=1.0.0 <1.1.0`
 - An OpenAI Codex login in Pi
 
 Restart Pi after upgrading its runtime. `/reload` reloads extensions but cannot
 upgrade the running Pi process. At load time, the extension requires the host's
 transcript APIs, the Pi 0.99 APIs `SessionManager.getEntryCount()` and
-`ExtensionAPI.getSettings()`, and a reported Pi version of at least 0.99.1. It
+`ExtensionAPI.getSettings()`, and a reported Pi version of at least 1.0.0. It
 refuses to load otherwise. The load check does not reject newer releases: the
-`<0.100.0` bound is the package's peer range, which Pi does not enforce when it
+`<1.1.0` bound is the package's peer range, which Pi does not enforce when it
 installs packages. `PI_PACKAGE_DIR` can point an older executable at
 newer package metadata, so the reported version alone does not establish
-compatibility. The API checks cover that case.
+compatibility. The API checks detect missing capabilities from before Pi 0.99.
+They do not distinguish a Pi 0.99 executable from Pi 1.0.0 when its metadata
+points at the newer installation.
 
 Authenticate through Pi if needed:
 
@@ -288,7 +290,6 @@ Defaults:
 
 Responses Lite supports exactly `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-5.6-luna`,
 `gpt-6-astra`, `gpt-6-sol`, `gpt-6-luna`, and `gpt-6.1-sol`. It remains opt-in.
-GPT-6.1 Sol requires Pi 0.99.1's model catalog.
 
 Invalid JSON setting values are ignored and invalid JSON does not prevent Pi from
 starting. The settings pane reports malformed JSON instead of overwriting it.
@@ -669,7 +670,7 @@ npm run pack:dry
 `mise run check` runs the linters, formatters, type checks, and the offline
 test suite; `mise run test` runs only the offline suite. Both tasks bind
 `PI_PACKAGE_DIR` to `node_modules/@earendil-works/pi-coding-agent`, so tests
-that load Pi in-process read this repository's Pi 0.99.1 resources even when a
+that load Pi in-process read this repository's Pi 1.0.0 resources even when a
 global `PI_PACKAGE_DIR` points at another installation. Ordinary `pi` launches
 outside these tasks are unaffected. Offline tests also exercise
 `scripts/release.ts` with every child process mocked: they never run Git, npm,
@@ -687,11 +688,14 @@ mise run test:live:codex
 The task obtains the local Codex bearer token and runs the tests with
 `gpt-5.6-luna`, `gpt-6-sol`, `gpt-6-luna`, and `gpt-6.1-sol` at medium reasoning
 effort. It also packs the extension and loads that archive through the shipped Pi
-0.99.1 CLI. Ordinary Responses and Responses Lite tests exercise tool calls,
+1.0.0 CLI. Ordinary Responses and Responses Lite tests exercise tool calls,
 prompt reload, native compaction, and persisted-session resume against Codex.
 SDK tests verify Responses Lite
 WebSocket history, prewarming, continuation, and the built-in read tool.
 CLI tests also execute the built-in read tool after resume.
+Six additional CLI cases replay grammar-tool history with `gpt-5.6-luna` in both
+response formats. They cover foreign-provider history, different-model history,
+and calls previously recorded as function calls.
 Test credentials stay in memory and child-process environments. Test sessions
 and configuration are isolated from the user's agent directory.
 
@@ -703,9 +707,9 @@ The packaged-CLI test selects its archive and executable as follows:
   existing regular file that `tar` can list, and an empty, missing, directory,
   or invalid value fails the test instead of falling back to a fresh pack.
 - `PI_CODEX_CLI_PATH` selects another Pi `cli.js`; the default is this
-  repository's Pi 0.99.1 dependency. The test asserts that the selected
-  executable reports version 0.99.1, the only Pi version the packaged CLI test
-  is run against. The supported range is `>=0.99.1 <0.100.0`.
+  repository's Pi 1.0.0 dependency. The test asserts that the selected
+  executable reports version 1.0.0, the only Pi version the packaged CLI test
+  is run against. The supported range is `>=1.0.0 <1.1.0`.
 - Each Pi child process receives `PI_PACKAGE_DIR` bound to the selected
   executable's package directory, so the runtime under test reads its own
   metadata.

package/extensions/openai-codex-compat/pi-runtime.ts

@@ -26,12 +26,12 @@ export const SESSION_APIS = ["buildSessionProjection"] as const;
 
 /**
  * Host APIs that first shipped in Pi 0.99: the footer's `SessionManager.getEntryCount()`
- * and the extension API's `getSettings()`. They prove the loaded runtime is 0.99 even when
- * `PI_PACKAGE_DIR` points package metadata at another installation.
+ * and the extension API's `getSettings()`. They detect missing pre-0.99 capabilities,
+ * not every mismatch between an executable and `PI_PACKAGE_DIR` metadata.
  */
 export const PI_099_APIS = ["SessionManager.getEntryCount", "ExtensionAPI.getSettings"] as const;
 
-export const MINIMUM_PI_VERSION = "0.99.1";
+export const MINIMUM_PI_VERSION = "1.0.0";
 export const REQUIRED_PI = `Pi ${MINIMUM_PI_VERSION} or later`;
 
 function isFunction(value: unknown): boolean {
@@ -62,9 +62,9 @@ export function atLeastVersion(version: unknown, minimum: string): boolean {
 }
 
 /**
- * Require the Pi 0.99 host surface and a reported version of at least 0.99.1. The version comes
- * from package metadata, so the API checks also run to catch an older executable whose
- * `PI_PACKAGE_DIR` names a newer package.
+ * Require the Pi 0.99 host surface and a reported version of at least 1.0.0. The version comes
+ * from package metadata. The API checks detect missing capabilities, but cannot distinguish
+ * a Pi 0.99 executable pointed at Pi 1.0.0 metadata through `PI_PACKAGE_DIR`.
  */
 export function requirePiRuntime(
   transcriptApi: Record<string, unknown>,

package/extensions/openai-codex-compat/vendor/pi-ai/README.md

@@ -4,6 +4,10 @@ This directory intentionally contains only the Pi AI methods needed to serialize
 
 [`openai-responses-serialization.ts`](openai-responses-serialization.ts) adapts the relevant methods from `@earendil-works/pi-ai@0.86.0`. Its header lists the upstream source files. It also carries the strict JSON-schema conversion from `src/api/constrained-sampling.ts`; Pi's built-in tools request strict sampling, and Codex rejects `strict: true` without that subset. Keep the wire-equivalence tests in [`test/pi-ai-serialization.test.ts`](../../../../test/pi-ai-serialization.test.ts) passing when updating the Pi dependencies.
 
+The copy also includes Pi 1.0.0's tool-call item-ID guard: same-model replay
+preserves valid `fc_` function IDs and `ctc_` grammar IDs, while incompatible
+item IDs are omitted without changing the `call_id` that pairs calls with results.
+
 Pi AI's transcript helpers replay system sections and tool declarations.
 `supportsAdditionalTools` and `supportsToolSearch` select the dynamic tool
 history representation for additive `toolsAdded` system messages:

package/extensions/openai-codex-compat/vendor/pi-ai/openai-responses-serialization.ts

@@ -826,10 +826,11 @@ export function convertResponsesMessages(
           const customInputProperty = options?.grammarToolInputProperties?.get(block.name);
           const namespaced = splitNamespacedToolName(block.name, options?.namespacedToolNames);
           let itemId = itemIdRaw;
-          if (
-            (isDifferentModel && itemId?.startsWith("fc_")) ||
-            (customInputProperty === undefined && !itemId?.startsWith("fc_"))
-          ) {
+          // Preserve item IDs only when they match the replayed tool type.
+          // Item IDs from another model of the same provider and API are always omitted.
+          // call_id still pairs every call with its result when an item ID is omitted.
+          const itemIdPrefix = customInputProperty === undefined ? "fc_" : "ctc_";
+          if (isDifferentModel || !itemId?.startsWith(itemIdPrefix)) {
             itemId = undefined;
           }
           if (customInputProperty !== undefined) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-openai-codex-compat",
-  "version": "0.0.19",
+  "version": "0.0.20",
   "description": "OpenAI Codex compatibility for Pi with native compaction, fast mode, and Codex-optimized capabilities",
   "keywords": [
     "pi-package"
@@ -51,9 +51,9 @@
   "devDependencies": {
     "@2h2d/oxlint-config": "0.1.1",
     "@2h2d/ts-config": "0.0.1",
-    "@earendil-works/pi-ai": "0.99.1",
-    "@earendil-works/pi-coding-agent": "0.99.1",
-    "@earendil-works/pi-tui": "0.99.1",
+    "@earendil-works/pi-ai": "1.0.0",
+    "@earendil-works/pi-coding-agent": "1.0.0",
+    "@earendil-works/pi-tui": "1.0.0",
     "@types/node": "22.20.1",
     "oxfmt": "0.64.0",
     "oxlint": "1.79.0",
@@ -62,9 +62,9 @@
     "typescript": "7.0.2"
   },
   "peerDependencies": {
-    "@earendil-works/pi-ai": ">=0.99.1 <0.100.0",
-    "@earendil-works/pi-coding-agent": ">=0.99.1 <0.100.0",
-    "@earendil-works/pi-tui": ">=0.99.1 <0.100.0",
+    "@earendil-works/pi-ai": ">=1.0.0 <1.1.0",
+    "@earendil-works/pi-coding-agent": ">=1.0.0 <1.1.0",
+    "@earendil-works/pi-tui": ">=1.0.0 <1.1.0",
     "typebox": "*"
   },
   "engines": {