Skip to content

pi-agent-browser-native 0.9.0

Choose a tag to compare

@fitchmultz fitchmultz released this 01 Oct 23:53
· 264 commits to main since this release

Browser modernization for Pi 1.0.0: native structured results, canonical failure status, cheap policy gates, and official native lifecycle qualification. Fork-only checkpoint/metadata/result-repair integration is removed on both 1.0 targets. Node 24.21.0, separately installed upstream agent-browser (0.38.1 recommended, 0.35.0 floor), and wildcard runtime peers are unchanged. Windows qualification remains owner-waived, not passed.

Breaking changes

  • Require Pi 1.0.0 or newer; Node 24.21.0 and separately installed upstream agent-browser requirements are unchanged. Pin the official development graph to 1.0.0 while retaining host-owned wildcard optional peers.
  • Remove Browser integration with dropped checkpoint and fork metadata/revision APIs. Keep stopped-copy legacy journal conversion, native save-on-close, browser/session replay and ownership-aware cleanup.

Changed

  • Use native defaultActive: false for the five advanced direct tools, retaining additive loader activation, explicit/defaultTools selections and the narrow official-1.0 initial-resume fallback.
  • Return canonical native isError and prose failure notices directly, without a result-repair hook; preserve explicit parseable JSON. Add native namespace/output-schema metadata and bounded redacted structured observations, loader inventory and normalized search results without exposing internal replay state or replacing the Browser code VM.
  • Skip irrelevant tool-event policy work; keep raw latest-user policy fresh through message completion and native content replacement. Reuse validated capture-local admission prefixes and one queued replay/launch-configuration fold, preserving publication checks and captured-leaf correctness. Skip unchanged per-row TUI formatting and text updates.
  • Replace the fork-only checkpoint CI gate with portable Native lifecycle Linux SDK qualification. Official/fork qualification remains independent; while the fork's main is below the supported Pi floor its lane emits a truthful unattempted-below-floor receipt and skips the fork build instead of resurrecting dropped APIs. Windows remains owner-waived, not passed.

Verification: strict four-name CI gate at merge head (Official Pi/Node 24, Fork Pi/Node 24 — full supported-fork qualification at fork main Pi 1.0.0 —, macOS package smoke, Native lifecycle Linux); 1,317 local default-verify tests with 0 failures; real-upstream, dogfood, package-pi, lifecycle, >1 GiB journal, startup (median 76.7 ms < 250 ms), TUI and real-site/Electron smokes; four independent final reviews approved.