v0.1.16 — ACP 1.4 model selection and safe recovery

v0.1.16 — ACP 1.4 model selection and safe recovery

Tested with Pi 1.3.0 and Node.js >=22.19.0. Stable ACP protocol 1 / SDK 1.8.0 remain unchanged. Pi host dependencies remain wildcard peers; the paired development packages are now pinned to 1.3.0.

Fixes

• Support Antigravity ACP 1.4.x split model and thought-level selectors. Discovery exposes effort-qualified IDs for Pi's reasoning controls; selection sends the base ID and effort separately and confirms both (#48, #50, integrated in #52; fixes #49).
• Recognize category-less thinking_level / thought_level aliases consistently. Match the live selector inventory, including additional levels such as off, while preserving exact native model IDs.
• Reach the older session/set_model fallback when a selector silently ignores a value. Preserve real authentication, timeout, abort and transport errors and their causes instead of replacing them with a generic selection failure.
• Reject disappearing or ignored effort selectors and model drift during effort updates. Discard warm and saved bindings after failed model changes so a partially changed base cannot silently service the next request under a stale model ID.
• Derive discovery from live selectors rather than stale, base-only or duplicate legacy metadata. Retain legacy labels only when the full, duplicate-free inventory matches.
• Add explicit Argon fallback entries while retaining Gemini 3.8 Flash as the conservative offline/default choice. This does not grant Argon access to ineligible accounts.

Runtime and dependencies

• Include signed Antigravity ACP runtime approvals through 1.4.1 (#44, #45).
• Update the paired Pi development dependencies to 1.3.0 and compatible dependencies, including security updates to Hono and transitive ip-address (#46, #47, #51, #52).
• Correct the documented Pi development/test version; Node.js requirements, default yolo permissions and automatic runtime-update behavior are unchanged.

Validation and limits

• Typechecking and 292 ordinary tests pass, including 14 added unit cases and 18 real-child-process integration cases. Eight opt-in official-runtime/live tests remain skipped during ordinary CI.
• Seven key new integration regressions fail on the unchanged #48 head and pass with the coordinated fixes.
• All three official-runtime contract tests pass against Antigravity ACP 1.4.1, including selection of every advertised model/effort and restoration of the original selection. No inference prompt was sent.
• Both supported Node CI lines validate typechecking, tests, package contents, isolated packed installation and the full dependency audit. Release validation also exercises npm 12 packaging.
• Full dependency audit reports zero vulnerabilities at release validation time.
• Synthetic tests and metadata-only checks do not establish inference entitlement, new-account OAuth success, or cross-platform macOS/Windows qualification. The provider is not a sandbox.

Thanks to @danielosman and @fatcutegg for the complementary model-selection fixes.

v0.1.15 — Reliability, context safety and reasoning metadata

v0.1.15 — Reliability, context safety and reasoning metadata

Requires Pi 1.1.x and Node.js >=22.19.0, unchanged from v0.1.14. Stable ACP protocol 1 / SDK 1.8.0 and the signed runtime catalog remain unchanged.

Fixes

• Preserve MCP tool input constraints, including literal/falsy constants and supported numeric/collection bounds. Omit unrepresentable tools rather than silently widening their schemas. Bound depth, traversal work and UTF-8 output; handle cycles, shared graphs, custom validators, proxies/accessors and annotation defaults safely. Original call-time validation remains the authorization boundary (#42).
• Preserve the active request and its images outside truncatable context reconstruction. Retain active tool-loop call/result identities and fence untrusted history, with an independent bounded history/delta budget. Preserve current Pi transcript system sections and the existing 256 KiB instruction limit; avoid replaying requests already delivered to warm sessions (#42).
• Keep single-tier Gemini models marked as reasoning-capable, with only the server-advertised tier and exact ID. This fixes the misleading non-thinking warning for Argon Medium; it does not unlock Argon for ineligible accounts or invent Low/High variants (#42).
• Reuse saved macOS OAuth credentials when a refreshable file exists but the consumer keychain entry does not. Honor the effective child HOME/GEMINI_HOME/API-key environment, use consistent scoped paths for setup/inspection/logout, and label credential diagnostics as preflight expectations (#40).
• Harden cancellation, parked tool/permission cleanup, asynchronous initialization/shutdown, warm-session policy confirmation, continuation instruction updates and omitted-tool diagnostics. Prompt deadlines track progress rather than total duration, with finite stuck-work recovery. Preserve full system instructions and adapt child-only HTTP proxies while bypassing them for authenticated loopback MCP traffic (#39).
• Update the GitHub Actions Node setup action (#41).

Validation and limits

• Clean install, typechecking and 254 enabled tests pass; eight opt-in official-runtime/live tests remain skipped in ordinary CI.
• Both supported Node CI lines validate checks, package contents, isolated packed installation and the full dependency audit.
• Local packed installation and full dependency audit pass with zero vulnerabilities. Release validation also exercises npm 12 packaging.
• An official ACP 1.3.0 metadata-only probe confirmed the advertised gemini-4-argon-medium ID and successful selection. No inference prompt was sent; catalog visibility is not proof of inference entitlement.
• Google currently lists Argon for AI Ultra and eligible Enterprise subscriptions, not AI Pro. No claim is made that this release fixes Google's plan gating, staged rollout or backend errors.
• Live Google inference, new-account OAuth, native-tool execution and cross-platform macOS/Windows qualification are not implied by synthetic tests. Default yolo permissions and automatic runtime updates remain unchanged; the provider is not a sandbox.

v0.1.14 — Compatibility and protected automation fixes

Compatibility and protected automation fixes

Requires Pi 1.1.x and Node.js >=22.19.0, unchanged from 0.1.13.

• Upgrade to TypeScript 7.0.2. Real cross-process session-store tests now use esbuild instead of removed compiler APIs (#31; resolves #23).
• Upgrade ACP SDK to current 1.8.0 on stable protocol 1, not experimental ACP v2. Support grouped session configuration options, stable resume, model/mode selection and config updates, while retaining validated backward compatibility with older official Antigravity model APIs (#32; resolves #29).
• Publish signed runtime updates through PRs, explicitly run both Node CI jobs, and merge only the exact checked head through active main-branch protection (#33/#36; resolves #27).
• Report the actual dispatched validation results with their job URLs, handling GitHub's bot-PR approval-pending suites without invented passes, admin bypasses or long-lived credentials.
• Protect main against direct/force pushes and deletion, require up-to-date PRs and both Node checks, and preserve the signed daily updater. No ruleset bypass actors.

Validation

• 146 enabled tests pass; 8 opt-in real/live tests remain skipped in regular CI.
• Node 22.19.0 and 24 CI, isolated packed installation, and full npm audit passed (zero vulnerabilities).
• Official installed Antigravity initialization, model discovery and model selection probes passed; no real prompt or coding-agent action was sent.
• The protected bot merge path was exercised successfully in #37 using only whitespace around an already-signed catalog. The signed payload and approved runtimes did not change.
• The normal daily-update workflow also passed after the migration.

All original blocked upgrade PRs and the branch-protection issue are resolved.

v0.1.13 — Security and Pi 1.1 compatibility

Maintenance release

Compatibility: update Pi first. This release targets Pi 1.1.x and requires Node.js >=22.19.0. Pi host packages remain unbundled peers.

Changes

• Upgrade MCP SDK to 1.32.1 and refresh vulnerable transitive dependencies, including ip-address, proxy-addr, fast-uri and source-map-js. Both production and full development audits are clean.
• Upgrade both Pi development packages together to 1.1.0. Replay native transcript instructions, named sections and tool additions/removals into ACP checkpoints, invalidating stale warm sessions when state changes.
• Validate tool arguments against Pi's stricter JSON contract.
• Support PI_CODING_AGENT_DIR for configuration and persisted ACP bindings (#13, thanks @iamxeph). Existing custom settings are preserved. Initial migration copies permission/update settings only; Antigravity OAuth accounts and managed runtimes remain shared.
• Add Node 22.19/24 PR CI, weekly grouped Dependabot updates, and packaging/packed-install/full-audit gates before trusted npm publication.
• Support npm 12 pack output in the isolated packed-install smoke test; update Vitest, TypeBox, GitHub Actions checkout and Node 24 declarations.

Verification

• 124 tests passing; 7 explicitly opt-in live/real-runtime tests skipped.
• Node 22.19.0 and 24 CI passed.
• Clean npm 12.2.0 install, packaging and packed-provider registration passed.
• Full npm audit reports zero vulnerabilities; no open GitHub Dependabot security alerts at release review.

Follow-ups

• TypeScript 7 requires a concurrency-test harness migration (#23).
• Bot-aware main-branch protection must preserve signed daily runtime updates (#27).

No real authenticated Google prompts were run during this maintenance release.

v0.1.12 — NixOS standalone and TLS fixes

Fix Google Antigravity ACP startup and TLS trust on NixOS and standalone Pi builds.

• Run the ACP supervisor with Node rather than recursively launching a standalone Pi executable. Honor explicit NODE wrappers (including NixOS/nonstandard names), recognize nodejs, search the child PATH, and report a clear error if Node is unavailable.
• Pass a readable CA bundle from NIX_SSL_CERT_FILE or standard system paths through the supervisor to the ACP runtime, while preserving explicit SSL_CERT_FILE.
• Add a combined standalone Pi + Nix-style Node override + symlinked CA regression test and document the Home Manager Node configuration.

Verification: npm run check (102 passed, 7 skipped), packed-install smoke test, and successful GitHub Actions npm publish with provenance. Live NixOS/Google authentication was reported by the PR contributor; it was not re-run for this release.

v0.1.11 — Antigravity runtime update

Accept the new Antigravity archive naming in the signed runtime manifest and approve the latest ACP runtime. Published to npm as pi-antigravity-acp-provider@0.1.11 with provenance. Typecheck and tests passed.

v0.1.10 — cancellation and multi-instance fixes

Fix ACP connection-closed crashes when model catalog refresh is cancelled. Make discovery initialization cancellable and observe cancellation notification failures. Serialize shared session-store mutations across Pi processes with stale-lock recovery. Includes cancellation and multi-process regression tests. Typecheck, 76 tests, and packed-install verification passed; 7 opt-in live tests skipped.

v0.1.9

Full Changelog: v0.1.8...v0.1.9

v0.1.8

Remove personal contact metadata and machine-specific documentation paths. No runtime behavior changes.

v0.1.7

Full Changelog: v0.1.5...v0.1.7