Cursor CLIAnysphereCursor CLI, off your laptop — sign in and it’s yours.
The agent from the Cursor editor, on a machine of its own. One click boots a fresh microVM where Cursor CLI installs itself and stops at its real sign-in gate — the boot on this page is the actual capture. Sign in with your own Cursor account and it’s yours; we bill machine time only and never see your Cursor usage.
rapid-volereal first boot · captured live on zipbox.ai · sign in with your Cursor account and it’s yours — we never see your Cursor usageCursor CLI source ↗
How you set up Cursor CLI in the cloud
Sign in
Email if you want it simple, a crypto key if you want anonymity. No passwords — every session is cryptographically signed.
Boot Cursor CLI
A fresh Firecracker microVM boots and Cursor CLI installs and launches itself at first boot, stopping at its real sign-in gate. No key to paste, no metered proxy — sign in with your own Cursor account.
It’s live in your browser
A full-root terminal opens in the browser and the box answers at its own zbox.sh subdomain. Pause parks it for free, delete wipes it for good, SSH is optional.
Questions, answered straight
- Do I need a Cursor account to run Cursor CLI?
- Yes — Cursor CLI runs on your own account — sign in inside the sandbox at first boot. We bill machine time only. Model usage lands on your own Cursor plan — zipbox never sees it — and there is no pay-per-use option: Cursor CLI routes only through Cursor’s backend, so a metered key can’t reach it.
- What does running Cursor CLI in the cloud cost?
- $0.0342 per hour while the sandbox runs — about $25 a month left on 24/7 — and $0 while it’s paused. You start with free credit — no card. Cursor CLI’s default machine is 2 vCPU · 4 GB RAM · 80 GB disk, and other sizes start at $10/mo.
- What happens when I pause or delete a Cursor CLI sandbox?
- Two buttons, honestly: Pause shuts the machine down and parks its disk for free — restore it later and pick up where the agent left off. Delete wipes the whole VM — disk, memory, network — permanently. You only ever pay while it runs.
- Is it safe to let Cursor CLI run unattended with full permissions?
- In a sandbox, yes — that’s the point. The box is a hardware-isolated Firecracker microVM with its own kernel and none of your files, keys, or cookies. Close the tab and it keeps working; the blast radius is one disposable machine.
- Can I SSH into the sandbox?
- Optionally. The browser terminal is the default and needs no setup. Add an SSH public key when you boot and you can also connect from your own terminal — same machine, same session.
every agent zipbox boots
Pi
Claude Code
Codex
Grok
Hermes
OpenClaw
opencode
ClineCursor CLI, on a machine you can throw away.
One click boots Anysphere’s terminal coding agent on a disposable cloud machine — and you pay only while it runs.