Skip to main content

Zeq for Chrome

Zeq for Chrome brings the physics virtual machine into your browser as a side panel — compute, contracts, a live Observer, CKO envelopes, and page security checks, on the same machine identity as the web and the VS Code extension.

Install​

  1. Download and unzip the file above.
  2. Open chrome://extensions, toggle on Developer mode.
  3. Click Load unpacked and select the unzipped folder.
  4. Pin Zeq from the toolbar and open the side panel.

Side panel​

  • Compute — operator chains → value + ZeqProof; every result can append to your chain.
  • Contracts — deploy templates and watch state transitions.
  • Observer — a live chain feed that ticks every Zeqond (777 ms), new rows flash, your machine highlighted.
  • CKO widget — the same CKO envelope analysis as the editor, brand-themed (mint on black).
  • Protocols / Skills / Pulse — browse the live protocol set, the skills library, and the 1.287 Hz pulse.
  • Security — ZSP / HITE / SSL / AV checks give a page-safety verdict for whatever you're browsing.
  • Vault — your keys and secrets, HITE-encrypted in chrome.storage.local.

Workbench + ZeqGit, in-panel​

The side panel hosts the full web Workbench, the ZeqGit dashboard, and the Observer directly in-panel (signed in on your machine via the auth bridge — no second login). So the per-project repo system is right there in the browser: the name-your-app prompt, a unique private repo per chat, automatic file / page / state-contract save with a ZeqProof on every commit, and the file-aware dashboard — the same surface as the web, reused rather than re-implemented, so it never drifts from the editor or the web. Open it from the panel's ⚛ Workbench and ZeqGit buttons.

Same rules, everywhere​

Like every Zeq surface, the Chrome client keeps KO42 first, never fabricates a value, labels awareness operators as speculative, holds precisionBound ≤ 0.1%, and measures time in Zeqonds. Secrets never touch a .env file — they're HITE-encrypted in chrome.storage.local.