← Latest papers
🔬 physics

Perspective on AI and quantum open-source software

This paper argues that establishing rigorous verification practices and contribution standards is essential to ensure the reliability of AI-assisted quantum open-source software development, thereby mitigating maintainer burdens and enabling reproducible, trustworthy quantum research.

Original authors: Changhao Li, Bradley A. Chase, Veena Vijayakumar, Mathys Rennela, Alessandro Cosentino, Naixu Guo, Sebastian Hassinger, Farrokh Labib, Seun Omonije, Patrick Rebentrost, Vincent Russo, Nathan Shammah
Published 2026-10-30
📖 6 min read🧠 Deep dive

Original authors: Changhao Li, Bradley A. Chase, Veena Vijayakumar, Mathys Rennela, Alessandro Cosentino, Naixu Guo, Sebastian Hassinger, Farrokh Labib, Seun Omonije, Patrick Rebentrost, Vincent Russo, Nathan Shammah, William J. Zeng, Ben Castanon

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). ✨ This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Quantum information science is a rapidly growing field that seeks to harness the strange rules of the subatomic world to solve problems that are impossible for today's computers. This science relies heavily on software to build circuits, run simulations, and control the delicate hardware that holds quantum bits. For years, this software has been built and shared openly by a global community of researchers, allowing anyone to inspect, improve, and build upon the work. Recently, artificial intelligence has begun to reshape this landscape. These intelligent tools can write code, suggest new ways to calibrate machines, and even help discover new methods for correcting errors. However, just as a new engine needs a new set of safety checks, the introduction of artificial intelligence into this high-stakes environment has raised a critical question: how do we know the code these tools write is actually correct, and who is responsible for checking it?

A team of researchers from the Unitary Foundation and the Centre for Quantum Technologies has taken a close look at this emerging reality. They examined how artificial intelligence is currently being used to write and maintain quantum software, and they analyzed the burden this places on the human volunteers who keep these projects running. By studying public code repositories, records from five annual hacking events, and surveying more than 1,600 members of the community, the researchers found that while artificial intelligence is a powerful helper, it is also creating a hidden bottleneck. The study reveals that without strict new rules for verification, the very people who keep quantum software safe are being overwhelmed by the need to check work they did not write, a situation that threatens to slow down scientific progress and erode the trust required for open collaboration.

The researchers began by mapping out exactly where artificial intelligence is being used in the quantum software stack. They found that these tools are already helping with everything from writing basic code and optimizing how circuits are compiled to designing control pulses for hardware and even discovering new ways to correct errors. In some cases, artificial intelligence agents are working in loops, proposing solutions, testing them, and refining their approach to reach a scientific goal. This "auto-research" approach holds great promise for accelerating discovery. However, the team noted a significant gap: while the tools are getting better at generating ideas and code, the methods for verifying that these outputs are scientifically valid have not kept pace. For quantum software, verification is uniquely difficult because checking the answer often requires simulating the entire system, a task that becomes impossible for classical computers once the system grows beyond a few dozen particles.

To understand the real-world impact of this gap, the team looked at the data. They analyzed thousands of files from public repositories and found that the quantum software community is much smaller and less stable than mainstream software communities. While mainstream libraries are downloaded millions of times a month, quantum libraries see far fewer downloads, and the code that uses them is often less visible. More importantly, they discovered that the tests used to check this code are almost always run on tiny, simplified versions of the problems. In the test suites of major quantum frameworks, the median number of particles used in a test is just two, and nearly all tests involve twenty or fewer. This means that the safety nets currently in place are designed for small, manageable problems and may fail to catch errors that only appear when the system scales up to the sizes needed for real scientific work.

The human element of this story is perhaps the most urgent. The researchers surveyed the community and found that when artificial intelligence generates code, the burden of checking it falls heavily on the project maintainers. In a recent survey, 79 percent of respondents said they relied on manual review to verify code written by artificial intelligence, while only 60 percent used automated tests. This reliance on human eyes is creating a shift in how community events are run. Organizers of annual hackathons reported that the time spent mentoring new contributors is being replaced by time spent reviewing submissions that may be generated by artificial intelligence. One maintainer described the experience as talking to an artificial intelligence tool through the interface, rather than guiding a human learner. The data suggests that while artificial intelligence can speed up the completion of tasks, it does not necessarily help new contributors learn the skills they need to become future maintainers, and it risks turning the review process into a bottleneck that slows down the entire field.

The paper argues that the solution lies in establishing new standards for how contributions are made and verified. The researchers propose that anyone submitting code, whether written by a human or an artificial intelligence, must provide reproducible evidence that their changes work. This means that instead of just submitting a fix, contributors should include the specific tests and data that prove the fix is correct. They suggest that projects should use specialized tools that can verify the logic of a circuit without needing to simulate the entire system, and that these tools should be part of the standard review process. The team also recommends that projects create clear boundaries for artificial intelligence agents, ensuring they cannot spend money on hardware or install dangerous software without human approval. By making verification a routine part of the workflow, the community can ensure that the results produced by artificial intelligence are reliable and can be trusted by other scientists.

Ultimately, this work is about preserving the integrity of scientific discovery in an age of automated assistance. The researchers maintain an open-source companion repository to help projects adopt these new practices, providing templates and tools to make verification easier. They envision a future where software contributions are treated with the same rigor as journal articles, where the evidence supporting a claim is as important as the claim itself. By combining the speed of artificial intelligence with the rigor of independent verification, the quantum community can continue to push the boundaries of what is possible without losing the trust and collaboration that make open science work. The study concludes that while artificial intelligence is a powerful tool for exploration, it is the human commitment to verification that will determine whether the discoveries it helps make are real.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →