CUDA-Q Guide
Purpose
Guide users through CUDA-Q installation, basic kernels, GPU simulation targets,
QPU access, built-in applications, multi-GPU execution, and Python
@cudaq.kernel authoring. For Qiskit-to-CUDA-Q ports, route to the
qiskit-to-cudaq skill instead.
Prerequisites
- Python 3.10+ for Python CUDA-Q workflows.
- CUDA Toolkit and an NVIDIA GPU for GPU-accelerated targets on Linux.
- CPU-only simulation is available through
qpp-cpu; macOS is CPU-only.
- C++ workflows require Linux or WSL and C++20.
- QPU workflows require provider-specific credentials and accounts.
Instructions
- Invoke with
/cudaq-guide [argument].
- If no argument is given, display the onboarding menu and ask which topic the
user wants.
- Use the routing table below to choose the relevant reference file.
- Read local CUDA-Q documentation files when the answer depends on a specific
CUDA-Q version or backend behavior.
- Do not answer Qiskit porting questions from this skill; use
qiskit-to-cudaq.
Routing by Argument
| Argument |
Action |
Reference |
install |
Walk through Python or C++ installation and validation. |
references/onboarding.md |
test-program |
Build and run a Bell-state kernel. |
references/onboarding.md |
gpu-sim |
Select GPU, multi-GPU, tensor-network, or CPU targets. |
references/onboarding.md |
qpu |
Guide provider selection and credential-safe QPU setup. |
references/onboarding.md |
applications |
Summarize CUDA-Q application areas and notebooks. |
references/onboarding.md |
parallelize |
Choose mgpu, mqpu, async dispatch, or distributed observe. |
references/onboarding.md |
author |
Author CUDA-Q Python kernels, select execution APIs, and debug compiler issues. |
references/authoring.md |
| (none) |
Print the menu below and ask which topic to explore. |
This file |
Menu
CUDA-Q Getting Started
CUDA-Q is NVIDIA's unified quantum-classical programming model for CPUs, GPUs, and QPUs.
Supports Python and C++. Docs: https://nvidia.github.io/cuda-quantum/latest/
Choose a topic:
/cudaq-guide install Install CUDA-Q
/cudaq-guide test-program Write and run a Bell-state kernel
/cudaq-guide gpu-sim Accelerate simulation on NVIDIA GPUs
/cudaq-guide qpu Connect to real QPU hardware
/cudaq-guide applications Explore what you can build
/cudaq-guide parallelize Run across GPUs or QPUs
/cudaq-guide author Author @cudaq.kernel Python code
Reference Files
- references/onboarding.md: installation, test
program, GPU targets, QPU providers, application areas, parallelization
modes, examples, and platform troubleshooting.
- references/authoring.md: execution APIs,
kernel-language constraints, silent-failure pitfalls, recurring coding
patterns, resource metrics, debugging, and validation.
Limitations
- Guidance targets CUDA-Q Python/C++ workflows, with authoring details focused
on decorator-mode Python APIs used in CUDA-Q 0.14 and 0.15.
- GPU and multi-GPU support depends on local CUDA-Q, CUDA Toolkit, driver, MPI,
and hardware availability.
- QPU access and target options are provider-specific and may change; verify
against local docs before giving operational steps.
Troubleshooting
- Import error after
pip install cudaq: check Python 3.10+ and supported
OS.
- No GPU detected: verify CUDA Toolkit and
nvidia-smi; fall back to
qpp-cpu.
- Kernel compile error: read references/authoring.md
and check the restricted kernel-language subset.
- Version-specific behavior differs: compare
cudaq.__version__ with the
latest documentation, then review relevant documentation or source changes
when debugging an installed version that is not the latest release.
- QPU submission fails: verify provider credentials are set as environment
variables or through a secrets manager, never hardcoded.
- Documentation lookup fails: retry transient MCP or repository lookup once,
then fall back to local docs or official CUDA-Q documentation.
1---2name: cudaq-guide-33description: Use for CUDA-Q setup, simulation targets, QPU access, and @cudaq.kernel authoring guidance.4license: Apache-2.05---67# CUDA-Q Guide89## Purpose1011Guide users through CUDA-Q installation, basic kernels, GPU simulation targets,12QPU access, built-in applications, multi-GPU execution, and Python13`@cudaq.kernel` authoring. For Qiskit-to-CUDA-Q ports, route to the14`qiskit-to-cudaq` skill instead.1516## Prerequisites1718- Python 3.10+ for Python CUDA-Q workflows.19- CUDA Toolkit and an NVIDIA GPU for GPU-accelerated targets on Linux.20- CPU-only simulation is available through `qpp-cpu`; macOS is CPU-only.21- C++ workflows require Linux or WSL and C++20.22- QPU workflows require provider-specific credentials and accounts.2324## Instructions2526- Invoke with `/cudaq-guide [argument]`.27- If no argument is given, display the onboarding menu and ask which topic the28 user wants.29- Use the routing table below to choose the relevant reference file.30- Read local CUDA-Q documentation files when the answer depends on a specific31 CUDA-Q version or backend behavior.32- Do not answer Qiskit porting questions from this skill; use33 `qiskit-to-cudaq`.3435## Routing by Argument3637| Argument | Action | Reference |38|---|---|---|39| `install` | Walk through Python or C++ installation and validation. | [references/onboarding.md](references/onboarding.md) |40| `test-program` | Build and run a Bell-state kernel. | [references/onboarding.md](references/onboarding.md) |41| `gpu-sim` | Select GPU, multi-GPU, tensor-network, or CPU targets. | [references/onboarding.md](references/onboarding.md) |42| `qpu` | Guide provider selection and credential-safe QPU setup. | [references/onboarding.md](references/onboarding.md) |43| `applications` | Summarize CUDA-Q application areas and notebooks. | [references/onboarding.md](references/onboarding.md) |44| `parallelize` | Choose `mgpu`, `mqpu`, async dispatch, or distributed observe. | [references/onboarding.md](references/onboarding.md) |45| `author` | Author CUDA-Q Python kernels, select execution APIs, and debug compiler issues. | [references/authoring.md](references/authoring.md) |46| _(none)_ | Print the menu below and ask which topic to explore. | This file |4748## Menu4950```text51CUDA-Q Getting Started5253CUDA-Q is NVIDIA's unified quantum-classical programming model for CPUs, GPUs, and QPUs.54Supports Python and C++. Docs: https://nvidia.github.io/cuda-quantum/latest/5556Choose a topic:57 /cudaq-guide install Install CUDA-Q58 /cudaq-guide test-program Write and run a Bell-state kernel59 /cudaq-guide gpu-sim Accelerate simulation on NVIDIA GPUs60 /cudaq-guide qpu Connect to real QPU hardware61 /cudaq-guide applications Explore what you can build62 /cudaq-guide parallelize Run across GPUs or QPUs63 /cudaq-guide author Author @cudaq.kernel Python code64```6566## Reference Files6768- [references/onboarding.md](references/onboarding.md): installation, test69 program, GPU targets, QPU providers, application areas, parallelization70 modes, examples, and platform troubleshooting.71- [references/authoring.md](references/authoring.md): execution APIs,72 kernel-language constraints, silent-failure pitfalls, recurring coding73 patterns, resource metrics, debugging, and validation.7475## Limitations7677- Guidance targets CUDA-Q Python/C++ workflows, with authoring details focused78 on decorator-mode Python APIs used in CUDA-Q 0.14 and 0.15.79- GPU and multi-GPU support depends on local CUDA-Q, CUDA Toolkit, driver, MPI,80 and hardware availability.81- QPU access and target options are provider-specific and may change; verify82 against local docs before giving operational steps.8384## Troubleshooting8586- **Import error after `pip install cudaq`:** check Python 3.10+ and supported87 OS.88- **No GPU detected:** verify CUDA Toolkit and `nvidia-smi`; fall back to89 `qpp-cpu`.90- **Kernel compile error:** read [references/authoring.md](references/authoring.md)91 and check the restricted kernel-language subset.92- **Version-specific behavior differs:** compare `cudaq.__version__` with the93 latest documentation, then review relevant documentation or source changes94 when debugging an installed version that is not the latest release.95- **QPU submission fails:** verify provider credentials are set as environment96 variables or through a secrets manager, never hardcoded.97- **Documentation lookup fails:** retry transient MCP or repository lookup once,98 then fall back to local docs or official CUDA-Q documentation.