Skip to main content

VS Code & Chrome extensions

The framework ships two first-party clients that put the physics VM inside the tools you already use — no context switch, one identity across the editor, the browser, and the web. Both connect to your real machine, run real compute with a verifiable ZeqProof, and work with or without an AI.

Zeq for VS Code​

The full ZeqVM dashboard inside your editor: author and fire state contracts, run compute, browse protocols and operators, manage skills, and install from a large library — all without leaving your project. And your workspace folder is a ZeqGit repo: every change is versioned, every commit anchored with a ZeqProof.

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 — so you can build and publish a channel app from the same window you're browsing in.

One identity, one workspace​

Same machine everywhere

Sign in once; the same ZeqID, contracts, observer, and credits are there in the editor, the browser, and on the web.

Versioned automatically

Whatever you build in either client is a ZeqGit repo — one shared module names the repos identically across every surface, so they never drift.

AI-optional

Both work fully by hand. An AI is an accelerator, not a requirement — the physics and proofs are the same either way.