PUBLISHED // CHROME WEB STORE // CONSENT-FIRST MANIFEST V3

Tab Pilot

Let your self-hosted OpenZero node work inside one Brave tab that you explicitly grant. OpenZero Gemma plans one bounded action at a time; the extension performs it locally and keeps a visible stop control on the page.

Version 0.2.0 · signed CRX SHA-256 8584330a1f9776de927469a148bda0ba1539e6259b7ef389a12ea9d8a6742a7e · extension ID bjjhckhjkjodankbndllgloanjnfmlmo

What it can do

  • Inspect a privacy-reduced page snapshot.
  • Navigate, click, type, select, scroll, wait, go back, and go forward.
  • Use scoped model discovery and a strict browser-only planner.
  • Stop and revoke immediately from Brave or the page overlay.

Authority stays local

  • Every tab needs an explicit user grant.
  • New origins need a Brave permission prompt.
  • Consequential clicks and personal-data entry need one-time confirmation.
  • Passwords, payments, secrets, CAPTCHAs, uploads, and arbitrary JavaScript are blocked.

Linux: installed and updated automatically

On desktop Linux, OpenZero 7.1 installs Brave from Brave's official installer when it is missing, then configures the signed extension through Brave managed policy. It creates a browser-planner-only token, keeps the main API key untouched, and registers the self-update feed. Headless servers install no browser unless --brave is passed. Opt out with --no-tab-pilot.

curl -fsSL https://openzero.talktoai.org/install.sh | bash
# Existing node:
curl -fsSL https://openzero.talktoai.org/update.sh | bash

For an existing local checkout, one command performs the same scoped setup:

cd ~/openzero && ./install-tab-pilot.sh

Almost-automatic Windows setup

The helper downloads the fixed extension archive, verifies its built-in SHA-256, extracts it under your local application-data folder, opens brave://extensions, and shows the exact folder to load. Brave deliberately keeps the final Load unpacked approval manual.

Invoke-WebRequest https://openzero.talktoai.org/install-tab-pilot.ps1 -OutFile "$env:TEMP\install-openzero-tab-pilot.ps1"
powershell -NoProfile -ExecutionPolicy Bypass -File "$env:TEMP\install-openzero-tab-pilot.ps1"
  1. Review the downloaded script if you prefer.
  2. Enable Developer mode in the Brave page opened by the helper.
  3. Choose Load unpacked and select the displayed folder.
  4. Open extension Options and connect it to your OpenZero API.

Remote node? Add its SSH name and the helper can create a current-user Windows startup connection:

powershell -NoProfile -ExecutionPolicy Bypass -File "$env:TEMP\install-openzero-tab-pilot.ps1" -OpenZeroSshHost user@your-server -ConfigureTunnel

Connect securely

For OpenZero on another machine, keep its API bound to loopback and create a tunnel:

ssh -N -L 1024:127.0.0.1:1024 your-openzero-server

Then configure Tab Pilot with http://127.0.0.1:1024. Managed Linux installs use a planner-only token; manual installs store the configured token in extension-local storage. Neither is injected into page JavaScript.

One default. Two optional Qwen builds.

Tab Pilot starts with the verified OpenZero Gemma model. The Qwen variants are visible choices for operators who want to experiment, but neither is downloaded or made default automatically.

DEFAULT · 5.46 GiB

OpenZero Gemma

openzerogemma:latest
Verified Q5_K_M/F16 merged release for the standard OpenZero lane.

Open on Hugging Face →
OPTIONAL · 5.45 GiB

Qwen3 8B Q5

zero-qwen3-q5:latest
Smaller quantized Qwen experiment. Install from the Super Panel only when wanted.

Open on Hugging Face →
OPTIONAL · 13.82 GiB

Qwen3 8B F16

zero-qwen3-f16:latest
Full fused F16 Qwen experiment for machines with the storage and memory headroom.

Open on Hugging Face →
OpenZero Tab Pilot is now published in the Chrome Web Store. The self-hosted signed CRX and verified ZIP remain available for managed Linux deployments, offline recovery, and source-verifiable testing. Use it only on pages you control or are authorized to operate; site rules and final-action responsibility still apply.