pi-cursor-sdk 0.1.57 → 0.1.59

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## 0.1.59 - 2026-07-16
+
+### Changed
+
+- Migrate stored Cursor API-key reads from the removed root `AuthStorage` export to the Pi 0.80.9 `readStoredCredential()` contract, accepting only stored `api_key` credentials before the existing environment fallback.
+- Build extension test contexts through an isolated async `ModelRuntime` and `ModelRegistry` compatibility facade, and refresh exact Pi development dependencies to 0.80.9 while preserving wildcard runtime peers.
+
+## 0.1.58 - 2026-07-14
+
+### Changed
+
+- Update the Pi development and validation baseline to 0.80.7, including Pi's 372k GPT-5.6 Codex metadata, and expose opt-in `max` thinking only when Cursor advertises a distinct `max` value.
+- Wait for Pi's final-idle `agent_settled` RPC event in smoke/debug harnesses instead of stopping at a low-level `agent_end` that may precede retries or queued work.
+
 ## 0.1.57 - 2026-07-10
 
 ### Changed
@@ -39,11 +53,6 @@
 - Reject local resume handles that cross user messages already persisted at process startup, preventing a hard-crash restart from resending a prompt that the prior Cursor agent may already have accepted.
 - Reject non-HTTPS and credential/query/fragment-bearing Cursor Cloud repository URLs before `Agent.create()`, and redact URL/SCP-style userinfo from provider and maintainer output.
 
-### Validation
-
-- Current offline evidence is limited to the checked-in focused tests, full unit suite, platform-smoke syntax/tooling checks, and TypeScript checks; final command results belong in the release artifacts/status.
-- Required and pending release gates are `npm publish --dry-run`, `npm run smoke:platform:all`, `npm run smoke:cloud`, and the applicable live release smokes. Their final results belong in the release artifacts/status, not this changelog.
-
 ## 0.1.56 - 2026-07-04
 
 ### Changed

package/README.md

@@ -51,10 +51,10 @@ If pi started without a key, run `/cursor-refresh-models` after `/login` to refr
 ## Requirements
 
 - Node.js 22.19+
-- pi 0.80.5 or newer recommended; pi core peer metadata is intentionally unpinned so newer pi releases are not blocked
+- pi 0.80.9 or newer recommended; pi core peer metadata is intentionally unpinned so newer pi releases are not blocked
 - a Cursor SDK API key saved through `/login`, available as `CURSOR_API_KEY`, or passed with pi's `--api-key`
 
-No global `@cursor/sdk` install is required. This package depends on exact `@cursor/sdk@1.0.23`, so normal package installation brings in the SDK version this extension was built and tested against. Cursor SDK 1.0.23 declares its Node ConnectRPC transport dependency directly, so npm installs place `@connectrpc/connect-node` where the SDK can resolve it. The extension intentionally does not bundle `@cursor/sdk` or its platform packages, because packing from one maintainer OS can otherwise ship the wrong optional SDK binary for another OS. Cursor SDK 1.0.23 keeps the older `sqlite3 -> node-gyp@8` dependency chain out of the runtime tree, so deprecated install warnings for `inflight`, `rimraf`, `glob@7`, `npmlog`, `gauge`, `are-we-there-yet`, and `tar@6` from that chain are not expected. This package follows pi package guidance by declaring pi core package peers with `"*"` ranges, so users who update pi before this extension is republished are not blocked by peer metadata. The current recommended and validated pi baseline is 0.80.5 plus Cursor SDK 1.0.23; older pi compatibility paths are best-effort and older Cursor SDK compatibility paths are not maintained.
+No global `@cursor/sdk` install is required. This package depends on exact `@cursor/sdk@1.0.23`, so normal package installation brings in the SDK version this extension was built and tested against. Cursor SDK 1.0.23 declares its Node ConnectRPC transport dependency directly, so npm installs place `@connectrpc/connect-node` where the SDK can resolve it. The extension intentionally does not bundle `@cursor/sdk` or its platform packages, because packing from one maintainer OS can otherwise ship the wrong optional SDK binary for another OS. Cursor SDK 1.0.23 keeps the older `sqlite3 -> node-gyp@8` dependency chain out of the runtime tree, so deprecated install warnings for `inflight`, `rimraf`, `glob@7`, `npmlog`, `gauge`, `are-we-there-yet`, and `tar@6` from that chain are not expected. This package follows pi package guidance by declaring pi core package peers with `"*"` ranges, so users who update pi before this extension is republished are not blocked by peer metadata. The current recommended and validated pi baseline is 0.80.9 plus Cursor SDK 1.0.23; older pi compatibility paths are best-effort and older Cursor SDK compatibility paths are not maintained.
 
 ## Install
 
@@ -178,7 +178,7 @@ How to read model IDs:
 
 - `cursor/...` is the Cursor provider registered by this extension
 - `@1m`, `@272k`, and `@300k` are context-window variants
-- `:medium`, `:high`, and `:xhigh` are pi thinking-level suffixes for models where the Cursor SDK exposes a pi-controllable thinking parameter
+- `:medium`, `:high`, `:xhigh`, and `:max` are pi thinking-level suffixes for models where the Cursor SDK exposes the corresponding pi-controllable thinking parameter
 - unambiguous latest-style Cursor aliases returned by `Cursor.models.list()` are registered too, using the same context suffixes when the target model has context variants; aliases shared by multiple base models or colliding with a base model ID are skipped because their SDK resolution and displayed metadata can diverge
 
 Examples with pi thinking controls:
@@ -186,6 +186,7 @@ Examples with pi thinking controls:
 ```bash
 pi --model cursor/gpt-5.5@1m:medium
 pi --model cursor/gpt-5.5@272k:xhigh
+pi --model cursor/claude-opus-4-7@1m:max
 pi --model cursor/gpt-5.5@1m --thinking medium
 ```
 
@@ -201,6 +202,8 @@ For models where Cursor exposes `reasoning`, `effort`, or boolean `thinking` par
 - `effort=low|medium|high|xhigh|max`
 - `thinking=false|true` for boolean thinking models
 
+Pi `xhigh` maps to Cursor `xhigh` or `extra-high`; Pi `max` maps only to a distinct Cursor `max` value.
+
 For Claude models with both `thinking` and `effort`, pi thinking `off` sends `thinking=false` and omits `effort`.
 
 ### Why some Cursor models show `thinking=no`

package/docs/cursor-live-smoke-checklist.md

@@ -67,8 +67,8 @@ The replay scan flags only error `toolResult` / error assistant messages with `T
 
 Pass criteria:
 
-- `pi --version` reports pi 0.80.5 for this cutover baseline.
-- `npm ls` shows `@cursor/sdk@1.0.23` and local `@earendil-works/*@0.80.5` packages.
+- `pi --version` reports pi 0.80.9 for this cutover baseline.
+- `npm ls` shows `@cursor/sdk@1.0.23` and local `@earendil-works/*@0.80.9` packages.
 - `cursor/composer-2-5` appears in the model list.
 - No Cursor key or auth token is printed.
 - If neither `~/.pi/agent/auth.json` cursor auth nor `CURSOR_API_KEY` is available, stop and report the live smoke as blocked.
@@ -125,7 +125,7 @@ Observe with `tmux capture-pane -pt "$SESSION"` or attach manually.
 Pass criteria:
 
 - Footer shows `(cursor) composer-2-5`. With `--cursor-no-fast`, Cursor fast mode is off and the Cursor extension status should show `cursor:local · fast:off`; ignore unrelated status text from other extensions.
-- The run uses pi 0.80.5 `--session-id` successfully.
+- The run uses pi 0.80.9 `--session-id` successfully.
 - Assistant answer appears correctly.
 - `/session` shows one user and one assistant message for the simple run.
 - Persisted JSONL has one assistant message. If the screen appears duplicated, inspect JSONL before deciding whether it is a rendering bug.
@@ -133,7 +133,7 @@ Pass criteria:
 
 ## 4. Focused visual card/color rendering check
 
-This is the canonical inner-loop visual debug path for Cursor provider/runtime changes. It requires offscreen TUI visual inspection, not only JSONL or code review. Use pi 0.80.5, `@cursor/sdk@1.0.23`, a fresh temporary session dir, Cursor SDK `plan` mode, native replay enabled, and the checked-in visual runner. The runner resolves `pi` by directly walking the parent `PATH`, uses `process.execPath` for Node, and prepends that Node directory for both prereq checks and tmux launches so `#!/usr/bin/env node` shims use the validated Node. The default matrix is native replay only: native replay registration is forced on, settings sources are `none`, the pi bridge is off, overlapping built-in pi tools are not exposed, and inherited Cursor SDK event-debug artifact env is cleared. With `--event-debug`, debug capture writes to a deterministic directory under `VISUAL_DIR`.
+This is the canonical inner-loop visual debug path for Cursor provider/runtime changes. It requires offscreen TUI visual inspection, not only JSONL or code review. Use pi 0.80.9, `@cursor/sdk@1.0.23`, a fresh temporary session dir, Cursor SDK `plan` mode, native replay enabled, and the checked-in visual runner. The runner resolves `pi` by directly walking the parent `PATH`, uses `process.execPath` for Node, and prepends that Node directory for both prereq checks and tmux launches so `#!/usr/bin/env node` shims use the validated Node. The default matrix is native replay only: native replay registration is forced on, settings sources are `none`, the pi bridge is off, overlapping built-in pi tools are not exposed, and inherited Cursor SDK event-debug artifact env is cleared. With `--event-debug`, debug capture writes to a deterministic directory under `VISUAL_DIR`.
 
 ```bash
 VISUAL_DIR="$(mktemp -d /tmp/pi-cursor-sdk-1016-visual.XXXXXX)"

package/docs/cursor-model-ux-spec.md

@@ -15,7 +15,7 @@ Current implementation notes:
 - Cursor status uses one coordinated `ctx.ui.setStatus("cursor", ...)` value for fast and non-default plan mode; the default pi footer remains intact.
 - Installed `@cursor/sdk` user messages accept images, and Cursor models are treated as image-capable; registered input metadata is `text` plus `image`.
 - Image payload forwarding sends images only from the latest user message. If the latest user turn is plain text after an earlier image turn, the transcript keeps an `[image omitted from transcript]` placeholder but no image bytes are sent to Cursor. The prompt explicitly tells Cursor that prior image bytes are unavailable and to ask the user to reattach or describe a prior image when needed. Carrying images forward across turns remains a future product decision because it affects token cost, privacy, stale visual context, and expected multimodal follow-up behavior.
-- Exact `@cursor/sdk@1.0.23` is a package dependency of this extension; users should not need a global SDK install. pi 0.80.5 is the current recommended validation baseline, while published pi core peer dependencies use `"*"` ranges per current pi package guidance. Newer pi versions are allowed to attempt loading this extension before a matching extension release exists; compatibility is best-effort until validated.
+- Exact `@cursor/sdk@1.0.23` is a package dependency of this extension; users should not need a global SDK install. pi 0.80.9 is the current recommended validation baseline, while published pi core peer dependencies use `"*"` ranges per current pi package guidance. Newer pi versions are allowed to attempt loading this extension before a matching extension release exists; compatibility is best-effort until validated.
 - Startup discovery does not duplicate Pi CLI parsing: it uses stored `~/.pi/agent/auth.json` API-key auth from `/login`, then `CURSOR_API_KEY`, otherwise it registers the bundled fallback catalog. Provider turns keep Pi's resolved `options.apiKey`. `/cursor-refresh-models` and `/cursor-cloud` mutations resolve provider `cursor` through the command context's Pi ModelRegistry, then normalize placeholders through `CURSOR_API_KEY`. The extension config file stores only non-secret Cursor-only state such as fast defaults.
 - Cursor Cloud repository overrides accept only HTTPS repository URLs without userinfo, query parameters, or fragments. Invalid values fail during preflight before `Agent.create()`, messages never echo the supplied URL, and shared provider/maintainer scrubbing removes URL/SCP-style userinfo defensively.
 - Cursor Cloud requires a persisted pi session. Immediately after remote `Agent.create()` returns, before debug work or abort checks, the provider appends a branch-local pi lifecycle entry, fsyncs the existing Pi session JSONL anchor through a read-write descriptor, and then fsyncs a newline-framed sidecar keyed by the stable pi session ID (POSIX mode `0600`; Windows inherits the user session directory ACL) in the session directory. Journal creation is exclusive, and existing append/read opens reject symlinks and require matching regular-file descriptor/path identity before using the descriptor. Existing session files use the exact lifecycle entry ID as anchor; fileless first turns use an orphan marker that a same-session-ID restart durably claims onto exactly one matching or replacement branch, surviving the timestamped path change and later JSONL creation without granting sibling access; returned run IDs are fsynced before abort/wait handling, readers skip malformed/truncated lines independently, and branch-only history events are reduced after deduplicated sidecar history, and tombstones are tracked before records exist. A durable sidecar result remains authoritative if its optional Pi mirror append fails; if the sidecar result itself fails, the prior durable intent remains pending and blocks retry rather than claiming success. `--no-session` and durable-ledger failures fail closed before send, while post-send ledger failure requests bounded cancellation. `/cursor-cloud` always validates the embedded session ID, accepts only null anchors while truly fileless, and reconciles each orphan to one branch before listing or mutation. Successive record events merge run/branch metadata monotonically even when mirrored sources arrive out of order. Archive/delete require resolved Cursor auth, fsync a durable intent before the SDK call, and fsync a durable success result afterward; unresolved intent blocks repeat mutation and requires dashboard inspection.
@@ -83,7 +83,7 @@ Cursor.models.list({ apiKey });
 
 Startup discovery resolves `apiKey` in this order:
 
-1. Stored pi auth for provider `cursor` from `AuthStorage.create().getApiKey("cursor", { includeFallback: false })`.
+1. Stored pi auth for provider `cursor` from `readStoredCredential("cursor")`, accepting only an `api_key` credential.
 2. `CURSOR_API_KEY`.
 
 Startup never parses `process.argv`; Pi remains the sole owner of CLI model/provider/key parsing. Provider turns keep Pi's resolved `options.apiKey`. Users can persist the stored key through `/login` -> `Use an API key` -> `Cursor`. If auth is added after startup, fallback models can run once Pi resolves the saved key for provider requests, and `/cursor-refresh-models` asks the command context's ModelRegistry for provider `cursor` and passes that normalized key explicitly to a forced live refresh.
@@ -276,7 +276,7 @@ Do not mark a model `reasoning: true` only because it can think. That would make
 Pi levels:
 
 ```text
-off, minimal, low, medium, high, xhigh
+off, minimal, low, medium, high, xhigh, max
 ```
 
 Cursor values vary by model. Build `thinkingLevelMap` from the values Cursor exposes.
@@ -290,18 +290,19 @@ Mapping rules:
 | `low` | `low` |
 | `medium` | `medium` |
 | `high` | `high`, else `true` for boolean-only thinking |
-| `xhigh` | `xhigh`, else `max`, else `extra-high` |
+| `xhigh` | `xhigh`, else `extra-high` |
+| `max` | `max` |
 
 Important details:
 
 - Use `null` for unsupported pi levels so pi hides/skips/clamps them natively.
-- Include `xhigh` only when Cursor exposes a real value for it.
-- Prefer exact `xhigh` over `max`. Cursor currently exposes both on some Claude models, and exact `xhigh` is the closer native mapping.
+- Include `xhigh` and `max` only when Cursor exposes real values for them.
+- Keep `xhigh` and `max` distinct. Cursor exposes both on some models, while `extra-high` remains an `xhigh` alias.
 - If Cursor exposes `reasoning=none`, map pi `off` to `none`.
 - If Cursor exposes `thinking=false`, map pi `off` to `false`.
 - `thinkingLevelMap` does not create Cursor SDK params by itself. It only controls pi-native behavior. The Cursor stream implementation must use the active pi thinking level plus the extension's discovered Cursor metadata to build `ModelSelection.params` for `Agent.create()`.
 
-For boolean-only `thinking`, unsupported pi levels must be explicit `null`; otherwise pi treats omitted non-`xhigh` levels as supported. Use this shape unless Cursor exposes richer values:
+For boolean-only `thinking`, unsupported pi levels must be explicit `null`; otherwise pi treats omitted non-`xhigh`/`max` levels as supported. Use this shape unless Cursor exposes richer values:
 
 ```ts
 {
@@ -311,6 +312,7 @@ For boolean-only `thinking`, unsupported pi levels must be explicit `null`; othe
   medium: null,
   high: "true",
   xhigh: null,
+  max: null,
 }
 ```
 
@@ -701,7 +703,8 @@ Before calling done:
    - `reasoning` mapping
    - `effort` mapping
    - boolean `thinking` maps to pi `off` / enabled levels
-   - pi `xhigh` preference order: `xhigh`, then `max`, then `extra-high`
+   - pi `xhigh` preference order: `xhigh`, then `extra-high`
+   - pi `max` maps only to Cursor `max`
    - session restore for Cursor-only state
    - global default state for Cursor-only state
    - unsupported no-op notifications
@@ -722,6 +725,7 @@ Before calling done:
 3. Print mode:
    - `pi --model cursor/gpt-5.5@1m:medium -p "Say ok only"`
    - `pi --model cursor/gpt-5.5@272k --thinking xhigh -p "Say ok only"`
+   - `pi --model cursor/claude-opus-4-7@1m --thinking max -p "Say ok only"`
    - `pi --model cursor/gpt-5.5@1m --cursor-fast -p "Say ok only"`
    - `pi --model cursor/gpt-5.5@1m --cursor-mode plan -p "Say ok only"`
    - confirm requests use selected context, pi thinking, fast flag state, and SDK-native mode

package/docs/cursor-native-tool-visual-audit.md

@@ -6,7 +6,7 @@ This workflow is the canonical repo path for verifying Cursor SDK tool replay th
 
 Use it before accepting replay-card commits or PRs, and for every Cursor provider/runtime release where TUI card/color behavior could regress. Text logs and JSONL are necessary, but they are not enough when the claim is visual parity: always keep PNGs for the exact prompt, and keep before/after PNGs when reviewing a rendering change.
 
-Current validation baseline: pi 0.80.5, exact `@cursor/sdk@1.0.23`, local validation packages `@earendil-works/pi-ai`, `@earendil-works/pi-coding-agent`, and `@earendil-works/pi-tui` at 0.80.5. Published pi core peer dependencies use `"*"` ranges per current pi package guidance, so newer pi installs can try the extension before a matching validation release exists.
+Current validation baseline: pi 0.80.9, exact `@cursor/sdk@1.0.23`, local validation packages `@earendil-works/pi-ai`, `@earendil-works/pi-coding-agent`, and `@earendil-works/pi-tui` at 0.80.9. Published pi core peer dependencies use `"*"` ranges per current pi package guidance, so newer pi installs can try the extension before a matching validation release exists.
 
 ## Cursor SDK 1.0.17 / pi 0.79.0 cutover visual record
 

package/docs/cursor-testing-lessons.md

@@ -256,7 +256,7 @@ The script writes timestamped artifacts under `--out` (default `/tmp/pi-cursor-s
 
 Stdout prints artifact paths and summary counts only. Raw payloads stay on disk and may contain local paths, project text, tool args/results, or secrets — do not commit or share them.
 
-Hard repo rule: Cursor SDK behavior claims must come from the installed `@cursor/sdk` package and/or https://cursor.com/docs/sdk/typescript, not from memory or ad-hoc probes alone. Current cutover validation targets exact `@cursor/sdk@1.0.23` and pi 0.80.5 local packages.
+Hard repo rule: Cursor SDK behavior claims must come from the installed `@cursor/sdk` package and/or https://cursor.com/docs/sdk/typescript, not from memory or ad-hoc probes alone. Current cutover validation targets exact `@cursor/sdk@1.0.23` and pi 0.80.9 local packages.
 
 ## Pi provider SDK event capture
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-cursor-sdk",
-  "version": "0.1.57",
+  "version": "0.1.59",
   "description": "pi provider extension backed by @cursor/sdk local and cloud agents",
   "author": "Mitch Fultz (https://github.com/fitchmultz)",
   "license": "MIT",
@@ -151,9 +151,9 @@
     "typebox": "*"
   },
   "devDependencies": {
-    "@earendil-works/pi-ai": "0.80.5",
-    "@earendil-works/pi-coding-agent": "0.80.5",
-    "@earendil-works/pi-tui": "0.80.5",
+    "@earendil-works/pi-ai": "0.80.9",
+    "@earendil-works/pi-coding-agent": "0.80.9",
+    "@earendil-works/pi-tui": "0.80.9",
     "@xterm/xterm": "^6.0.0",
     "node-pty": "^1.1.0",
     "playwright": "^1.60.0",

package/scripts/cloud-runtime-smoke.mjs

@@ -337,19 +337,19 @@ function startRpc({ artifactDir, contextHandoff, sessionId }) {
 	return { events, send, stop, get stderr() { return stderr; } };
 }
 
-async function waitForAgentEnd(rpc, fromIndex, timeoutMs) {
+async function waitForAgentSettled(rpc, fromIndex, timeoutMs) {
 	const started = Date.now();
 	while (Date.now() - started < timeoutMs) {
-		if (rpc.events.slice(fromIndex).some((event) => event.type === "agent_end")) return;
+		if (rpc.events.slice(fromIndex).some((event) => event.type === "agent_settled")) return;
 		await new Promise((resolveWait) => setTimeout(resolveWait, 250));
 	}
-	throw new Error(`timeout waiting for agent_end. Stderr: ${rpc.stderr}`);
+	throw new Error(`timeout waiting for agent_settled. Stderr: ${rpc.stderr}`);
 }
 
 async function promptAndRead({ rpc, artifactDir, message, timeoutMs, expectedContextHandoff }) {
 	const fromIndex = rpc.events.length;
 	await rpc.send("prompt", { message }, timeoutMs);
-	await waitForAgentEnd(rpc, fromIndex, timeoutMs);
+	await waitForAgentSettled(rpc, fromIndex, timeoutMs);
 	const textResponse = await rpc.send("get_last_assistant_text", {}, 120000);
 	if (!textResponse.success) fail("failed to read last assistant text", textResponse.error);
 	const latestMetadata = readLatestMetadataIfPresent(artifactDir);

package/scripts/debug-provider-events.mjs

@@ -248,7 +248,7 @@ export async function runDebugProviderEvents(args, envInput = process.env) {
 			const start = Date.now();
 			const tick = () => {
 				const events = parseJsonLines(stdout);
-				if (events.some((event) => event.type === "agent_end")) {
+				if (events.some((event) => event.type === "agent_settled")) {
 					resolve(events);
 					return;
 				}

package/scripts/lib/local-resume-smoke-harness.mjs

@@ -268,22 +268,22 @@ export async function withRpc(options, run) {
 	}
 }
 
-async function waitForAgentEnd(rpc, fromIndex, timeoutMs) {
+async function waitForAgentSettled(rpc, fromIndex, timeoutMs) {
 	const started = Date.now();
 	while (Date.now() - started < timeoutMs) {
-		if (rpc.events.slice(fromIndex).some((event) => event.type === "agent_end"))
+		if (rpc.events.slice(fromIndex).some((event) => event.type === "agent_settled"))
 			return;
 		await new Promise((resolveWait) => setTimeout(resolveWait, 250));
 	}
-	throw new Error(`timeout waiting for agent_end. Stderr: ${rpc.stderr}`);
+	throw new Error(`timeout waiting for agent_settled. Stderr: ${rpc.stderr}`);
 }
 
 async function waitForFile(path, timeoutMs, rpc) {
 	const started = Date.now();
 	while (Date.now() - started < timeoutMs) {
 		if (existsSync(path)) return;
-		if (rpc?.events.some((event) => event.type === "agent_end"))
-			fail(`agent ended before ${path} existed`, rpc.stderr);
+		if (rpc?.events.some((event) => event.type === "agent_settled"))
+			fail(`agent settled before ${path} existed`, rpc.stderr);
 		await new Promise((resolveWait) => setTimeout(resolveWait, 250));
 	}
 	fail(`timeout waiting for ${path}`, rpc?.stderr ?? "");
@@ -443,7 +443,7 @@ export async function promptAndRead({
 }) {
 	const eventStart = rpc.events.length;
 	await rpc.send("prompt", { message }, timeoutMs);
-	await waitForAgentEnd(rpc, eventStart, timeoutMs);
+	await waitForAgentSettled(rpc, eventStart, timeoutMs);
 	const text = await readLastAssistantText(rpc);
 	return {
 		text,
@@ -464,7 +464,7 @@ export async function promptAbortAndRead({
 	await rpc.send("prompt", { message }, timeoutMs);
 	await waitForFile(markerPath, timeoutMs, rpc);
 	await rpcData(rpc, "abort", {}, 120000);
-	await waitForAgentEnd(rpc, eventStart, timeoutMs);
+	await waitForAgentSettled(rpc, eventStart, timeoutMs);
 	return takeLatestMetadata(artifactDir, seenMetadata);
 }
 

package/scripts/steering-rpc-smoke.mjs

@@ -71,7 +71,7 @@ async function waitForChildCloseWithTimeout(child, timeoutMs, outputSummary = ()
 			new Promise((_, reject) => {
 				timeout = setTimeout(() => {
 					const summary = outputSummary();
-					reject(new Error(`pi did not exit within ${timeoutMs}ms after agent_end${summary ? `\n${summary}` : ""}`));
+					reject(new Error(`pi did not exit within ${timeoutMs}ms after agent_settled${summary ? `\n${summary}` : ""}`));
 				}, timeoutMs);
 			}),
 		]);
@@ -217,7 +217,7 @@ async function runPiRpcSmoke(sessionDir, piBin) {
 			() => stdout,
 			(events) => {
 				const text = assistantText(events);
-				return text.includes("STEER_OK=yes") && text.includes("STEER_CHAIN=ok") && events.some((event) => event.type === "agent_end");
+				return text.includes("STEER_OK=yes") && text.includes("STEER_CHAIN=ok") && events.some((event) => event.type === "agent_settled");
 			},
 		);
 
@@ -312,9 +312,9 @@ async function runSelfTest() {
 				await waitForChildCloseWithTimeout(hangingChild, 10, () => smokeOutputTail("STEER_OK=yes", ""));
 			} catch (error) {
 				const message = error instanceof Error ? error.message : String(error);
-				closeTimedOut = message.includes("pi did not exit within 10ms after agent_end") && message.includes("stdoutTail=STEER_OK=yes");
+				closeTimedOut = message.includes("pi did not exit within 10ms after agent_settled") && message.includes("stdoutTail=STEER_OK=yes");
 			}
-			if (!closeTimedOut) fail("self-test failed: post-agent_end child close wait should be bounded and report output tail");
+			if (!closeTimedOut) fail("self-test failed: post-agent_settled child close wait should be bounded and report output tail");
 		} finally {
 			if (originalPiBin === undefined) delete process.env.PI_BIN;
 			else process.env.PI_BIN = originalPiBin;

package/src/cursor-api-key.ts

@@ -23,8 +23,9 @@ export function resolveCursorApiKey(apiKey?: string): string | undefined {
 
 async function getStoredCursorApiKey(): Promise<string | undefined> {
 	try {
-		const { AuthStorage } = await import("@earendil-works/pi-coding-agent");
-		return resolveCursorApiKey(await AuthStorage.create().getApiKey(CURSOR_PROVIDER_ID, { includeFallback: false }));
+		const { readStoredCredential } = await import("@earendil-works/pi-coding-agent");
+		const credential = readStoredCredential(CURSOR_PROVIDER_ID);
+		return resolveCursorApiKey(credential?.type === "api_key" ? credential.key : undefined);
 	} catch {
 		return undefined;
 	}

package/src/model-discovery.ts

@@ -104,7 +104,7 @@ function mapComparableLevel(
 	level: Exclude<ModelThinkingLevel, "off">,
 ): string | null {
 	if (level === "xhigh") {
-		return getPreferredParameterValue(parameter, ["xhigh", "max", "extra-high"]);
+		return getPreferredParameterValue(parameter, ["xhigh", "extra-high"]);
 	}
 	return getParameterValue(parameter, level);
 }
@@ -124,6 +124,7 @@ function getThinkingLevelMap(item: ModelListItem): ThinkingLevelMap | undefined
 			medium: null,
 			high: getParameterValue(valueParameter, "true"),
 			xhigh: null,
+			max: null,
 		};
 	}
 
@@ -137,6 +138,7 @@ function getThinkingLevelMap(item: ModelListItem): ThinkingLevelMap | undefined
 		medium: mapComparableLevel(valueParameter, "medium"),
 		high: mapComparableLevel(valueParameter, "high"),
 		xhigh: mapComparableLevel(valueParameter, "xhigh"),
+		max: mapComparableLevel(valueParameter, "max"),
 	};
 }