Loading docs
Build Workflows
Generated Code
Review generated Qiskit, Cirq, and OpenQASM output beside the visual workflow before routing or exporting.
Updated May 26, 2026QFlow StudioNormal userTeacher
Generated code is not a separate product. It is a view of the same workflow record, useful for review, export, and collaboration with SDK-oriented teammates.
Use the code tab to verify that visual edits produce the expected source. Then route or export only after the code view matches the team’s intent.
Purpose
Review generated Qiskit, Cirq, and OpenQASM output beside the visual workflow before routing or exporting.
Where it fits
This page belongs to the Build Workflows section and should be read with the related pages listed at the end.
Review boundary
Use screenshots and notes to explain product behavior without exposing private credentials, admin state, or customer data.
Review code after visual edits
When a block property changes, return to generated code and confirm the source reflects the intended operation.
This is the best way to keep visual builders from becoming vague. The canvas shows intent; generated code confirms exact execution structure.
SDK target
Qubit count
Gate order
Measurement
Export format
AI builder still needs human review
The AI builder can draft a workflow path from plain English, but the output should remain inspectable. Treat generated source as a review surface, not as invisible automation.
Teams should verify the circuit, code, route fit, and review state before execution.
Next pages
Canvas
Use the QFlow Studio canvas to understand visual workflow blocks, connections, workflow switching, and responsive behavior.
Analysis & topology
Use analysis and topology views to understand circuit health, block depth, qubit structure, and provider fit before execution.
Providers
Select quantum providers, inspect hardware fit, and keep credentials private while routing workflows.