Loading Accelerated Logic…
GA Release

The Multi-Agent WebGPU Engine & Interactions API are now generally available.

Part 16: Browser Extension Packaging Status

The repository has an extension-layout flag, but the public build is not a ready-to-install browser extension.

Category: Companion Tools • Read Time: 6 min read • Updated: 2026-11-10

Status: no installable extension package is published

The ?extension=true query flag changes some workspace layout behavior. It does not create a Chrome or Edge extension, and the production build is not configured as a tested browser extension.

What the current app supports

Use Accelerated Logic AI as a regular website in a browser tab. The extension query flag is an internal layout option; it does not provide toolbar installation, keyboard shortcuts, access to the active tab, or storage shared with the website.

What the query flag and manifest sketch actually are

The repository carries two extension-adjacent artifacts. First, a ?extension=true query flag that adjusts some workspace layout behavior for a compact frame. Second, a sample Manifest V3 layout file describing a compact popup with activeTab and storage permissions. Popup dimensions belong in document styles, not non-standard manifest action fields. The sample exists to exercise the compact layout. It is not a build target: there is no release pipeline, packaged .crx/.xpi artifact, store listing, update mechanism, or tested side-loading path, and the production build is not wired to it.

  • The flag does not create a browser extension, does not register a toolbar action, and does not grant any permission beyond what the website already has as a website.
  • Side-loading the sample layout would show a cramped workspace, not a supported product — none of the extension-specific lifecycle (install, update, permission grant, uninstall cleanup) is implemented or tested.
  • Permissions in the sketch are aspirational documentation, not a grant: declaring activeTab in a file changes nothing for website visitors.

What a real release would require

A distributable extension needs all of the following before it could be announced, in roughly this order:

  1. A production manifest (V3) validated against the real built asset set — icons, paths, popup entry, and a reviewed content_security_policy compatible with the app's existing CSP.
  2. A deliberate permission review: every declared permission (activeTab, storage, host permissions) must map to a shipped, user-visible feature with a justification a store reviewer accepts.
  3. A storage and migration plan: how extension-local storage syncs with (or stays isolated from) the website's IndexedDB/localStorage world, and what happens to user data on uninstall.
  4. Cross-browser testing (Chrome, Edge, Firefox), including the compact popup UX at 420×600, keyboard navigation, and screen-reader behavior.
  5. Store assets, listing copy, privacy disclosure, and a security contact; then ongoing review maintenance for every permission or manifest change.
  6. A decision on update cadence and rollback — extensions update through the stores, not through the website's deploy pipeline.

None of those pieces is supplied by the current public build, which is why this page exists as a status note rather than an installation guide.

Supported alternatives today

  • Install as a PWA: the site ships a web app manifest (name, icons, display: standalone, theme colors), so supported browsers offer "Install Accelerated Logic AI" — a standalone window with its own storage profile, launchable from the OS like an app.
  • Pin the tab in your main browser profile; the workspace restores state from local storage, so the pinned-tab flow is effectively a persistent companion.
  • Mobile: the responsive layout and voice dictation (Part 14) cover quick on-the-go prompts without any install.

This page remains available as a direct status note while the feature is unshipped. Follow the regular workspace guides for supported browser workflows.