OpenZero Ministral 8B Runtime Agent
hf.co/shafire/OpenZero-Ministral3-8B-Runtime-Agent-GGUF:Q5_K_M
Verified OpenZero and browser-planning runtime. Upstream weights are unchanged.
Let your self-hosted OpenZero node work inside one Brave tab that you explicitly grant; the verified OpenZero runtime plans one bounded action at a time, the extension performs it locally, and a visible stop control stays on the page.
Managed/offline self-hosted package 0.2.0 · signed CRX SHA-256 8584330a1f9776de927469a148bda0ba1539e6259b7ef389a12ea9d8a6742a7e · extension ID bjjhckhjkjodankbndllgloanjnfmlmo
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
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"
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
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.
Tab Pilot starts with the same verified Ministral Q5 runtime as OpenZero. Gemma E4B remains available only for compatibility with existing nodes.
hf.co/shafire/OpenZero-Ministral3-8B-Runtime-Agent-GGUF:Q5_K_M
Verified OpenZero and browser-planning runtime. Upstream weights are unchanged.
openzerogemma:latest
Retained for existing deployments; it is never selected over the verified Ministral default automatically.