The lab, chapter by chapter.
The lab at lab.roroquantum.com is a VS Code-shaped editor with a phone line to real quantum machines. These are the same 13 chapters it shows inside the app — how projects, runs, credits, Python, notebooks, the library and Copilot actually behave — published here so a student, a professor, an evaluator or a researcher can read the whole thing first.
Thirteen short chapters, in reading order.
Each one is written from what the lab actually does — nothing aspirational. Chapters cross-link, and the last section is playbooks: read the one written for you.
Projects & files
Templates, folders, autosave, conflicts, tabs.
Read the chapterRun a circuit
QASM → quote → hardware confirm → result.
Read the chapterPython in the browser
The kernel, the SDK that is already there, its limits.
Read the chapterNotebooks
Cells, ⇧↵, Run all, %pip, outputs in the file.
Read the chapterCircuit builder & emulator
Draw the same file; scrub an ideal statevector.
Read the chapterLibrary
48 programs, five shelves (start-here row first), honest labels, fork.
Read the chapterCopilot
What it can and can't do, approvals, cost.
Read the chapterMachines & credits
Codenames, busy/online, quote, hold, settle, refund.
Read the chapterSharing & export
Snapshot links out, .zip in and out.
Read the chapterKeyboard shortcuts
Every binding, by surface.
Read the chapterThree things on screen.
The tour the lab offers on first visit, as text: Your file · Run it · Read the result. That is the whole surface.
Your file
This is the program — a .qasm circuit, a .py file or a notebook. Edit it here; everything autosaves. Your files are in the Explorer on the left.
Run it
The Run rail follows the active file. A .qasm gets a machine, shots and a price from the server, then Submit run; real hardware asks before it holds credits. A .py runs free in your browser with Run file.
Read the result
Output and run stories land here — a timeline, a histogram and one honest line about credits. Explain this result asks RoRo Copilot. ⌘J hides it.
Everything has a key.
The bindings that work everywhere in the lab. The full list — editor, notebook, circuit builder, explorer, gallery, Copilot — is one page.
Open the lab, or read the API docs.
The lab is where you prototype and read the catalogue; the Python client and the REST API are where an integration lives. Same run engine, same credits, same machine codenames everywhere.
- Learning on your own? Start with Getting started, then Run a circuit.
- Evaluating for a team? For teams & integration and Machines & credits.
- Measuring devices? For researchers, then talk to an engineer.