OpenZero 5.4 Book Edition
Local-first sovereign AI node, Super Panel, installer, Hive privacy, offline bundle, local models, API keys, and operator workflows.
Read the first pages once, then jump to the task-specific chapters.
OpenZero User Manual is designed as a stable online reader and a downloadable PDF. The reader keeps navigation without heavy scroll effects, and the PDF is clean, readable, and suitable for forwarding or printing.
The manual is based on public pages, local docs, and rollout notes.
These manuals consolidate the current public product story, live docs, release notes, and operational commands into a single readable book. They are intentionally public-safe.
A visual orientation page for the manual.
The image is not a screenshot. It is a visual map for the product: the control surface, protected assets, operating paths, and review mindset this manual teaches.
41 main chapters plus appendices.
Each chapter is short enough to scan but complete enough to act on. Use the page numbers in the PDF footer or the online jump links.
Later chapters cover operations, troubleshooting, support, and glossary.
The second half is built for real usage: what to check, what to avoid, and how to explain problems safely.
OpenZero is the local-first sovereign AI node path. It runs on user-controlled hardware and gives the user a private machine lane instead of relying entirely on hosted AI.
OpenZero is the local-first sovereign AI node path. It runs on user-controlled hardware and gives the user a private machine lane instead of relying entirely on hosted AI.
Cloud AI is convenient but sends prompts to provider infrastructure. OpenZero is designed for local operation, local state, and controlled sharing.
Cloud AI is convenient but sends prompts to provider infrastructure. OpenZero is designed for local operation, local state, and controlled sharing.
OpenZero 5.4 added cleaner website routes, Hive registration, RAM-aware node profiling, voice hooks, integrity manifest support, encrypted local node-state sealing, watchdog/doctor tooling, and offline release paths.
OpenZero 5.4 added cleaner website routes, Hive registration, RAM-aware node profiling, voice hooks, integrity manifest support, encrypted local node-state sealing, watchdog/doctor tooling, and offline release paths.
OpenZero depends on the hardware available. RAM, CPU, disk, GPU, and model size determine what is practical.
OpenZero depends on the hardware available. RAM, CPU, disk, GPU, and model size determine what is practical.
OpenZero has server, desktop, Kali, ISO, voice, and offline-aware paths in the broader release direction.
OpenZero has server, desktop, Kali, ISO, voice, and offline-aware paths in the broader release direction.
The public install route provides the online installer. Operators should run it on a clean supported Linux machine where possible.
The public install route provides the online installer. Operators should run it on a clean supported Linux machine where possible.
After installation, the first boot should confirm panel access, local process health, model availability, and basic prompt response.
After installation, the first boot should confirm panel access, local process health, model availability, and basic prompt response.
The Super Panel is the main local control and visibility surface. It should show node health, model state, terminal/log context, and operational controls where enabled.
The Super Panel is the main local control and visibility surface. It should show node health, model state, terminal/log context, and operational controls where enabled.
Local models are the brain lane for owner-controlled inference. Smaller quantized models are often more practical than huge downloads.
Local models are the brain lane for owner-controlled inference. Smaller quantized models are often more practical than huge downloads.
OpenZero offline and local model paths can include Ollama binaries and local model stores depending on the bundle/build path.
OpenZero offline and local model paths can include Ollama binaries and local model stores depending on the bundle/build path.
OpenZero can expose a node key path for tools that speak OpenAI-compatible APIs where configured.
OpenZero can expose a node key path for tools that speak OpenAI-compatible APIs where configured.
ZeroThink can use OpenZero nodes where bridge support is configured. This lets a user bring local compute into the web studio.
ZeroThink can use OpenZero nodes where bridge support is configured. This lets a user bring local compute into the web studio.
Hive coordination lets nodes report status and controlled public signals. It should not become surveillance.
Hive coordination lets nodes report status and controlled public signals. It should not become surveillance.
OpenZero privacy policy changed so Hive chat sharing is manual by default. Terminal-mode exchanges are blocked from manual Hive sharing because they may include commands, paths, secrets, or system output.
OpenZero privacy policy changed so Hive chat sharing is manual by default. Terminal-mode exchanges are blocked from manual Hive sharing because they may include commands, paths, secrets, or system output.
The local panel can support a send-last-chat-to-Hive pattern for deliberate sharing.
The local panel can support a send-last-chat-to-Hive pattern for deliberate sharing.
Moltbot represents the browser automation lane: navigation, screenshots, scraping, and OSINT-style observation when configured.
Moltbot represents the browser automation lane: navigation, screenshots, scraping, and OSINT-style observation when configured.
Terminal control is powerful and dangerous. OpenZero can be an agent with hands, so commands require caution.
Terminal control is powerful and dangerous. OpenZero can be an agent with hands, so commands require caution.
The Probability of Goodness idea is an alignment/risk scoring direction: commands should be evaluated for safety before execution.
The Probability of Goodness idea is an alignment/risk scoring direction: commands should be evaluated for safety before execution.
Watchdog tooling is for keeping the node alive and noticing failures.
Watchdog tooling is for keeping the node alive and noticing failures.
Doctor/self-healing tooling should inspect dependencies, service state, permissions, and common broken install points.
Doctor/self-healing tooling should inspect dependencies, service state, permissions, and common broken install points.
OpenZero runtime may use process managers such as PM2 in deployment flows. Operators need to know restart and log patterns.
OpenZero runtime may use process managers such as PM2 in deployment flows. Operators need to know restart and log patterns.
The runtime dependency set should stay lean: requests, colorama, Flask, Flask-SocketIO, psutil, cryptography, python-dotenv, and websockets were identified as the actual runtime set in the rollout notes.
The runtime dependency set should stay lean: requests, colorama, Flask, Flask-SocketIO, psutil, cryptography, python-dotenv, and websockets were identified as the actual runtime set in the rollout notes.
The offline release path is for machines that must continue running after physical disconnection from the internet.
The offline release path is for machines that must continue running after physical disconnection from the internet.
The connected builder node creates a tarball that carries source, Python wheelhouse, Moltbot node_modules, Node runtime archive, PM2 package, Ollama binary, local model store, and Chrome package where available.
The connected builder node creates a tarball that carries source, Python wheelhouse, Moltbot node_modules, Node runtime archive, PM2 package, Ollama binary, local model store, and Chrome package where available.
The offline target extracts and runs install_offline.sh. The installer treats the extracted folder as the final install directory unless a different directory is passed.
The offline target extracts and runs install_offline.sh. The installer treats the extracted folder as the final install directory unless a different directory is passed.
The offline bundle can become very large once model weights are included. Earlier guidance noted 15 GB to 25 GB for large air-gap bundles, while a live bundle was also recorded around 6.6 GB.
The offline bundle can become very large once model weights are included. Earlier guidance noted 15 GB to 25 GB for large air-gap bundles, while a live bundle was also recorded around 6.6 GB.
OpenZero 5.4 notes include voice hooks and optional offline voice wheels.
OpenZero 5.4 notes include voice hooks and optional offline voice wheels.
Some OpenZero docs mention BitNet/add-on style model experimentation. Treat experimental model lanes as optional and hardware-dependent.
Some OpenZero docs mention BitNet/add-on style model experimentation. Treat experimental model lanes as optional and hardware-dependent.
Some agent patterns include phone or remote control hooks. These must be secured and limited.
Some agent patterns include phone or remote control hooks. These must be secured and limited.
Node registration reports metadata such as node id, hostname, RAM profile, active model, node tier, paid-hive and voice flags.
Node registration reports metadata such as node id, hostname, RAM profile, active model, node tier, paid-hive and voice flags.
The public Hive monitor should show safe node/capability status and privacy counters, not private prompts or answers.
The public Hive monitor should show safe node/capability status and privacy counters, not private prompts or answers.
Federation mode adds Hive HQ plus backup mirrors and local continuity spool so nodes can survive operator/database loss.
Federation mode adds Hive HQ plus backup mirrors and local continuity spool so nodes can survive operator/database loss.
Server-side Hive filters reject script injection, destructive command, reverse shell, credential theft, and crypto-wallet theft patterns.
Server-side Hive filters reject script injection, destructive command, reverse shell, credential theft, and crypto-wallet theft patterns.
Encrypted local node-state sealing protects local identity/state material where configured.
Encrypted local node-state sealing protects local identity/state material where configured.
If the panel is down, check process manager, Python environment, port, logs, and recent updates.
If the panel is down, check process manager, Python environment, port, logs, and recent updates.
Slow local models usually mean hardware limits, model too large, context too high, or disk/memory pressure.
Slow local models usually mean hardware limits, model too large, context too high, or disk/memory pressure.
Hive registration can fail from endpoint, key, network, CORS, database, or stale config issues.
Hive registration can fail from endpoint, key, network, CORS, database, or stale config issues.
Offline install fails when base system requirements are missing, archive is corrupt, permissions are wrong, or the bundle was built without needed wheels/models.
Offline install fails when base system requirements are missing, archive is corrupt, permissions are wrong, or the bundle was built without needed wheels/models.
A working OpenZero node needs health, privacy, model, log, disk, and update checks.
A working OpenZero node needs health, privacy, model, log, disk, and update checks.
Teams should standardize node names, key owners, model policy, backup schedule, and update windows.
Teams should standardize node names, key owners, model policy, backup schedule, and update windows.
OpenZero terms map to operations: node is the machine, Super Panel is local control, Hive is coordination, Moltbot is browser hand, offline bundle is air-gap deployment, node key is API access.
OpenZero terms map to operations: node is the machine, Super Panel is local control, Hive is coordination, Moltbot is browser hand, offline bundle is air-gap deployment, node key is API access.
Use these only in the right context.
Commands and URLs are repeated here so operators can find them quickly. Read the chapter before running commands on production systems.
Run this before serious changes.
A manual is only useful when it changes behavior. This checklist is the calm-before-action page for live work.
Fast answers for the most common manual questions.
These answers are intentionally short. Use the chapter pages for operational detail.
Do the smallest useful next action.
OpenZero becomes easier when the next action is explicit. Pick the task, read the matching chapter, run a tiny verification, then scale up only after the first result works.