Release Notes: Chrome Extension 0.1.82

Version 0.1.82 adds template/data overlay assets to the Chrome extension and bookmarklet runtimes.

What Changed

  • overlay.open now accepts either inline html or a storage-backed template reference with an optional data reference.
  • Overlay templates and data can come from different storage scopes. A common pattern is a reusable public or shared template with private user data.
  • Template-driven overlays receive data through a trusted JSON script tag: <script type="application/json" data-actions-json-overlay-data>.
  • Template-driven overlays run in a sandboxed iframe with scripts enabled, so a template can read its data and render rich UI without page CSS collisions.
  • Inline HTML overlays keep the existing safer script-stripping path.
  • Downloading a template-driven overlay now produces a standalone HTML bundle containing the template, data JSON, and source metadata.
  • Uploading one of those bundles imports the template and data into private storage and reopens the overlay from private references.
  • The bookmarklet runtime has matching overlay.open, overlay.register_launcher, and overlay.close primitive coverage where the browser page permits it.

Why It Matters

Agents can now update overlay data without rewriting the visual template. That makes overlays easier to reuse, safer to share, and more useful for private workflows such as outreach dashboards, study notes, or site-specific reports.

The template can live in public or shared storage while the data stays private. When a user downloads the overlay, the runtime creates a portable bundle that still works outside the extension.

Verification

  • Added extension tests for public-template/private-data rendering.
  • Added extension tests for shared templates, missing assets, invalid JSON, and unsafe paths.
  • Added download/upload regression tests for standalone overlay bundles.
  • Added bookmarklet tests for storage-backed template/data overlays.
  • Updated the primitive dictionary tests so overlay primitives are covered as shared extension/bookmarklet capabilities.
  • Ran npm run test:runtime.
  • Ran npm run test:overlay-runtime.
  • Ran the extension Node test suite including package validation.