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 14 chapters it shows inside the app — how projects, runs, credits, Python, notebooks, the library and Copilot actually behave — published here so a hackathon organiser, an evaluator or a researcher can read the whole thing first.
Fourteen 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 & GitHub
Snapshot links out, read-only imports in.
Read the chapterKeyboard shortcuts
Every binding, by surface.
Read the chapterSeven things on screen.
The tour the lab offers on first visit, as text: The rail · Your project · Tabs · The Run rail · Output · Library · Copilot. That is the whole surface.
The rail
Nine doors, top to bottom: Explorer, Search, Library, Runs, Run rail, GitHub import, Integrate, Copilot, Guide. In the compact rail each icon names itself on hover; the bottom button shows or hides the names.
Your project
Files live here. Click to open, right-click for new / rename / delete; a slash in a file name makes a folder. Everything autosaves.
Tabs
Every open file is a tab — drag to reorder, middle-click to close. A .qasm tab gets a Code | Circuit toggle; a .py tab gets Run file once the Python kernel has loaded.
The Run rail
Follows the active file. A .qasm gets circuit, machine, shots and a server-priced quote; real hardware asks before it holds credits.
Output
Program output and run stories land here — a timeline, a histogram and one honest line about credits. Explain this result asks Copilot. ⌘J hides it.
Library
48 worked programs on five shelves — start with these, business cases, applications, algorithms, building blocks. ⌘K searches by subject. Open one to read its code; Open a copy makes it yours.
Copilot
Reads your project, proposes edits behind approval cards, runs Python locally. Metered per turn, no per-message cap — every cost lands in the feed as it settles, and it cannot spend run credits.
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 SDKs and the REST API are where an integration lives. Same run engine, same credits, same machine codenames everywhere.
- Running a hackathon? Start with For hackathons and Sharing & GitHub.
- Evaluating for a team? For teams & integration and Machines & credits.
- Measuring devices? For researchers, then talk to an engineer.