The machine's native terminal. Compute against the ZeqVM, sign in, build pages and applications, and drive state contracts — one command line, no model, no translator, no quota. Everything below runs against machine.zeq.dev.
Nothing to install. The terminal opens on load, bound to your machine. Type help, hit GUIDE for the walkthrough.
Prefer a real terminal? Install the single-file Node build (Node 18+), wired to this machine:
curl -fsSL https://cli.zeq.dev/install.sh | shDownloads zeqcli.mjs to ~/.zeq/, drops a zeqcli wrapper on your PATH, and binds it to machine.zeq.dev. Point it at any other Zeq node by exporting ZEQ_NODE first — the framework forks onto thousands of machines, and every one speaks the same surface:
ZEQ_NODE=https://your-node.example curl -fsSL https://cli.zeq.dev/install.sh | shzeqcli compute NM19 mass=5 acceleration=2login (drop your .zeq + PIN, decrypted in-browser) or signup "a memorable phrase, 4+ words". You become @your-zid, on your machine.compute NM19 mass=5 acceleration=2. Back comes a signed CKO envelope: value + units, the Zeqond it ran in, the ≤0.1% precision bound, an Ed25519 signature.page new myapp My First App scaffolds a live app into an in-terminal editor. Edit the HTML, hit preview, then publish.page open myapp → live at /s/<machine>/p/myapp/. Iterate with page edit myapp..zeq + PIN (in-terminal, decrypted locally)zeq_ak_ API key (shown once); keys list · keys revokecompute GR37 mass=1.98892e30operators show <OP> for one.zeq script filecompute GR37 mass=1.98892e30 --jsonSchwarzschild radius of the Sun as machine-readable JSON — pipe it to verify to check the signature and recompute.
login → page new landing → (edit + publish) → page open landingSign in, scaffold a page, publish from the editor, open it live — an app from the command line.
cli.zeq.dev · HulyaPulse 1.287 Hz · Zeqond 0.777000777 s · bound to machine.zeq.dev · open the terminal →