Equinox Browser 0.5.2

Reviewer test guide

Equinox Browser is a user-controlled Chrome bridge for the locally installed Equinox Local runtime. It uses Chrome Native Messaging and the debugger API for its declared browser-control purpose.

Reviewer build available. No OpenAI or other AI-provider account, subscription, API key, credentials, or private repository access is required. The limited reviewer runtime sends a fixed set of test commands through the same production Native Messaging bridge used by Equinox Local, while browser-data consent remains controlled by the real extension popup.

Download Equinox Local Reviewer 0.5.2

Package: macOS Apple Silicon + Intel installer · 19,514 bytes
SHA-256: 19e2585d413fa65b95f479f5137ce56c6fc6fd54a89e087cff937e174ec8a605

The installer downloads the pinned official Node.js 24.19.0 runtime from nodejs.org over HTTPS and verifies the architecture-specific SHA-256 checksum before installation. It will not replace an existing full Equinox Local Native Messaging host.

Single purpose

Connect the user's Chrome browser to their locally installed Equinox Local runtime so a user-authorized AI agent can inspect and interact with browser tabs, while the user retains a visible on/off control.

Expected setup

  1. Download and unzip equinox-local-reviewer-0.5.2.zip. Run Install Equinox Local Reviewer.command. This reviewer preview is not presented as a notarized public installer; if macOS blocks the first launch, Control-click the file and choose Open, or run it from Terminal.
  2. The installer registers Native Messaging host dev.equinox.browser only for production extension ID npdneefcobilfkjlihghjgjnknenhfoj, starts the loopback-only reviewer service, and opens http://127.0.0.1:24892/.
  3. Install/enable the Equinox Browser review package. Open its popup. Version 0.5.2 uses browser-data consent version 2 because the required bookmarks permission adds Agent Browser bookmark management; this patch does not add another permission or consent-version change. A previous consent version does not silently carry over; browser automation remains disabled until the updated disclosure is accepted and the reviewer explicitly chooses Enable browser control.
  4. Return to the local reviewer UI and run its smoke test. It opens the fixed public page Reviewer Browser Test, snapshots the page, finds Continue reviewer test, clicks it through Equinox Browser, and verifies Reviewer click passed on the success page.
  5. Use the separate status and tab-list controls if desired. No AI provider is involved in these reviewer commands.
  6. Turn browser control off in the extension popup. Browser automation commands must then be rejected while the Native Messaging settings channel can remain available.
  7. Turn browser control on again and repeat the smoke test. Current consent remains recorded; toggling control off does not silently revoke or re-grant consent.

What this build is

This is an intentionally limited Chrome Web Store reviewer companion, not the general public Equinox Local installer. It uses the real production browser bridge and Native Messaging host code, but replaces the normal AI-client decision layer with fixed reviewer buttons so extension behavior can be verified without third-party accounts, model subscriptions, or API keys.

Permissions under review

debugger performs the declared DevTools-based browser interaction; tabs identifies/activates/navigates supported tabs; downloads correlates user-requested downloads; nativeMessaging connects only to the local companion; alarms supports MV3 reconnect recovery; storage stores local user preferences and consent state; and required bookmarks manages saved sites/folders in the isolated Agent Browser profile. Equinox Local rejects bookmark automation for Your Browser before the request reaches Chrome, and the extension independently rejects bookmark commands unless its persisted browser context is Agent Browser. No broad host_permissions are requested.

Privacy reference

The canonical public policy is https://local.sametbasbug.dev/privacy/. The extension processes website content and browsing activity only for the requested browser-control feature. Data is sent first to the user's locally installed Equinox Local runtime; the user's chosen AI service may receive task-relevant information if needed to perform the requested action.