omnipkg v2.1.0 - Executable Documentation & Hybrid Local Cloud
Release v2.1.0 — Executable Documentation & Hybrid Local Cloud
OmniPkg is no longer just a package manager.
It is now an execution platform.
This release introduces Executable Documentation: a secure hybrid architecture that allows users to run real OmniPkg commands directly from the documentation website — with execution happening on their own machine, not in the cloud.
Static docs are dead.
Your environment is now the runtime.
🚀 What’s New
Executable Documentation
Documentation pages now include live Run buttons that execute the exact command being shown and stream real output back to the browser.
No copy/paste
No terminal switching
No “works on my machine”
If the docs show it, you can run it.
OmniPkg Web Bridge
A new local service that securely connects your browser to your machine:
Runs as a local Flask service
Executes commands in a constrained subprocess
Streams
stdout/stderrliveEnforces strict CORS and command allowlisting
Requires no open ports
Your browser becomes a remote control for your environment.
Hybrid Cloud–Local Architecture
OmniPkg now spans three layers — without centralizing compute:
Layer | Role -- | -- Cloudflare Pages | Static docs, UI, WASM, zero trust Cloudflare Worker | Edge proxy and request routing Local Bridge | Actual execution on the user’s machineExecution never leaves the user’s hardware.
Tailscale Remote Execution (Optional)
When the user is on the same Tailnet:
Commands can be executed from any device
Phone → Browser → Edge → Tailscale → Local machine
Fully end-to-end encrypted (WireGuard)
This enables:
Remote patching
Fleet demos
Live “watch this run” moments
Without SSH.
Without VPN configuration.
Privacy-First Telemetry (Local-Only)
Telemetry has been redesigned from the ground up:
Stored locally in
~/.omnipkg/telemetry.dbTracks command names and UI interactions only
No IP addresses
No environment data
No cloud persistence
You own your data. Period.
🧰 New CLI Commands
omnipkg web start # Start the local web bridge
omnipkg web stop # Stop it cleanly
omnipkg web status # Health, PID, uptime, URL
omnipkg web logs -f # Follow live execution + telemetry
The bridge is opt-in, visible, and fully controllable.
🔒 Security Model
Strict CORS enforcement
Explicit command allowlisting
No arbitrary shell execution
Local-only execution by default
Tailscale required for remote access
Cloud never executes user commands
This is zero-trust by design — not by marketing.
📈 Why This Matters
You did not just add a UI.
You created:
Executable documentation
Zero-infrastructure scaling
Local-first compute
Cloud-powered discovery
A clear path to paid orchestration features
This architecture supports:
Free local usage
Paid cloud-assisted workflows
Enterprise fleet control
Post-quantum machine identity (future)
Without ever centralizing user workloads.
📊 Release Stats
Files changed: 25
Insertions: 2,131
Deletions: 333
🏷 Versioning Decision
Bumped to v2.1.0
This release introduces:
A new execution surface
A new networking model
A new CLI namespace
A new telemetry architecture
This is a textbook minor version under SemVer.
🧭 What’s Next
Per-command executable documentation pages
Streamed output UI upgrades
Machine identity + JWT bridge (optional)
Paid cloud assist without forced cloud execution
OmniPkg docs are now alive.
They don’t explain commands.
They run them.
📥 How to Upgrade
The bridge and web UI are available immediately in v2.1.0.
# 1. Update OmniPkg
pip install --upgrade omnipkg
# 2. Launch the Web Bridge
omnipkg web start
# 3. Open the Docs & Start Clicking
# Your browser will automatically open to the local dashboard.Note:
flaskandflask-corswill be installed automatically if missing.
💬 Community & Feedback
This is a major architectural shift. We need your breakage reports, your "it works!" screams, and your security audits.
- GitHub: 1minds3t/omnipkg
- Docs: omnipkg.pages.dev
OmniPkg v2.1.0
The gap between "reading the docs" and "running the code" just vanished.