Quantum Software Tools
Our toolchain for writing N/M code, checking programs, simulating locally and inspecting results.
From software to results
This page describes current software and its usage limits. It does not establish a physical quantum processor, accelerator product or hardware access service.
01 / Toolchain
Parts that work together
Programming, learning and experiments meet around the same N/M runtime. Consult each guide for detailed support status.
N/M programming language
Build programs with quantum gates, measurement, supported classical values and functions. Consult the language guide for syntax and current scope.
N/M guideCode analysis
Inspect incompatibilities before execution with syntax, type and target capability checks. Diagnostic coverage varies by tool and feature.
Capability centreLocal simulation
Simulate supported circuits on a classical computer and inspect probabilities, measurements and runtime output. Memory and execution limits depend on the method.
Open PlaygroundEditor and command tools
The VS Code extension, language server, CLI and MCP tools support N/M development. Check the relevant guides for setup and distribution status.
VS Code and tooling guideLearning laboratories
Explore noise, error correction and circuit analysis with small examples. Some workflows use experimental models; read their assumptions and limits alongside results.
Explore laboratoriesExport and interoperability
Inspect export targets for supported program subsets. Generated code must be validated in its target environment; export does not guarantee execution on physical hardware.
View supported targets02 / Program path
From code to observable output
Follow the stages of an example and see how its results are produced.
- 01
N/M source
Define the circuit, classical values and experiment inputs in the program.
- 02
Analysis
Check syntax, types and target compatibility; inspect diagnostics alongside the source.
- 03
Execution
Run the program with a supported local simulation method or export to a suitable target.
- 04
Results
Interpret output, measurements and available circuit traces with the example’s assumptions.
Available features vary with the example, target and execution method. The capability centre documents each feature’s status and limits.
03 / Interpreting results
Limits of the results
An output reflects the chosen model and supported program scope.
Simulation capacity
Qubit count, noise models, measurement and classical control support vary by execution method. We do not promise one capacity or performance figure for all methods.
Physical hardware
Local simulation is not a real QPU measurement. Experimental connections such as provider adapters need separate configuration and actual provider validation; this page makes no hardware access commitment.
Comparison and estimates
Resource estimates are for education and circuit comparisons. Claims of quantum advantage, accuracy or speed require a suitable classical baseline, measurement method and experimental evidence.
Start with a small example
Choose an example from the language guide, run it in Playground and change its inputs. Consult the RFC archive for design decisions.