​
Overview

allternit-extensions ships the Allternit Chrome extension (allternit-extension) and its companion native host (native-host). Together they bring Allternit into the browser: agents can see the current page, drive it programmatically, and — through native messaging — reach the local Allternit runtime for file-system and system-level work.
For the Microsoft Office integration, see the dedicated Allternit Office Add-in page.

​
Chrome Extension (allternit-extension)

A unified Chrome extension built with WXT. It exposes Allternit agents directly inside the browser and on every webpage.

​
Features

  • Browser automation — Allternit agents can click, type, navigate, scroll, and extract data from the active tab using the same computer-use protocol as the rest of the platform.
  • Page agent — A floating chat panel is injected into any page so users can ask Allternit to act on what they are looking at.
  • Native messaging — The extension talks to the native-host bridge to forward actions to the local Allternit Desktop bridge on TCP 127.0.0.1:3011.

​
Development

​
Structure

​
Entrypoints

​
Native Host (native-host)

The native messaging host bridges the Chrome extension to the local system and the Allternit runtime. It is required for file system access and local agent execution from the browser. The host uses the single native messaging name:

​
Register the host

Chrome native messaging manifests require exact extension origins; wildcards are not allowed.
For direct shell usage you can also use the bundled script:

​
What the installer does

  1. Builds an executable wrapper at dist/allternit-native-host-wrapper.
  2. Writes com.allternit.desktop.json into supported Chromium native messaging host directories.
  3. Points the manifest path to the wrapper executable.
  4. Sets allowed_origins to the concrete chrome-extension://<id>/ origin.

​
Supported browsers

On macOS and Linux the installer registers the host for:
  • Google Chrome
  • Google Chrome for Testing
  • Microsoft Edge
  • Brave
  • Chromium
On macOS it also registers Arc. Windows registry wiring is handled separately.

​
Validation

smoke:browser-mode launches Chrome for Testing with the development extension, stages the native-host manifest into the temporary profile, starts a TCP 3011 bridge, and verifies that chrome.runtime.connectNative('com.allternit.desktop') reaches the host and returns pong.