Editor & browser tools
Zeq is a physics virtual machine. These first-party clients put it inside the tools you already use — no context switch, one identity across the web, the editor, and the browser.
| Client | What it is | Get it |
|---|---|---|
| Zeq for VS Code | The full ZeqVM dashboard inside your editor — state contracts, compute, protocols, operators, skills, a 70+ library installer, and ZeqGit (your workspace = a repo). | Download VSIX · App Store |
| Zeq for Chrome | The ZeqVM side panel in your browser — compute, contracts, a live Observer, page security checks, and the Workbench + ZeqGit hosted in-panel. | Download · App Store |
| ZeqGit | The framework's own git + PDF repository. Every project — a chat, a CLI contract, or a VS Code workspace folder — becomes a private repo; every commit is ZeqProof-anchored. | Open ZeqGit |
Both extensions are listed in the App Store under Developer, and install directly from the downloads above.
Everything you build in either client is versioned in ZeqGit automatically — your VS Code workspace folder, your Workbench projects, your state contracts — each a unique repo, each commit carrying a ZeqProof. One shared module drives the repo naming and IDs across the web, the editor, and the browser, so they never drift.
One identity, everywhere
Create an account or sign in once, and your machine — the same ZID, contracts, observer, and credits — is available in the editor, the browser, and on the web. Every surface offers Create Account on both tiers, not just sign-in. Three zero-friction identity methods:
- Simple — email + four words; the client generates one strong password.
- Expert — your Zeq ID + the equation you saved.
- .ZEQ — upload your encrypted recovery file + PIN; no password typed.
Creating an account never signs you in silently: first you get a screen to copy/save your generated password (or equation) and download your .ZEQ recovery file — there is no password reset, so that file is your only way back in.
AI-optional by design
You never need an AI to use Zeq. Every capability is a clickable surface. When you do use an AI, every prompt is first wrapped in the mandatory 7-step wizard (KO42 first) before any model sees it — so the framework grounds the request, not the model's guesswork.