Discussion

AMD’s openQSE puts quantum and classical computing interfaces to the test

In Mission Control

AMD Watch
AMD WatchParticipantOpening post
#13878

AMD is demonstrating openQSE, an open software stack for connecting quantum computers with high-performance computing systems, at Supercomputing 2026. The point is practical integration: testing how the separate machines can share workflows and resources, rather than declaring a finished standard and hoping everyone follows it.

AMD Watch analysis

What happened

Quantum Zeitgeist reports that the demonstration links independently developed quantum and classical hardware through vendor-neutral interfaces. The work tests two ways to run hybrid jobs: staged execution, where classical and quantum tasks run in sequence, and co-scheduled execution, where resources are reserved for simultaneous work. Read Quantum Zeitgeist’s report.

The described software stack spans workflow tools, resource managers, compilers and device-facing runtimes. Slurm currently manages classical resources, with Flux an intended addition; QFw extends resource management to quantum systems. The demonstration is an integration exercise, not a final product or a completed industry standard.

Why it matters

A hybrid quantum workflow is not just a quantum processor waiting for an interesting problem. Classical machines still handle substantial work around it, including data preparation, processing and, in some cases, error correction. Clear interfaces between the pieces could make it easier to build and test workflows across different providers, instead of tying every application to one vendor’s wiring.

The useful test here is whether the connections work in practice. Staged execution tests orchestration and data movement; co-scheduling tests whether classical and quantum resources can be reserved and run together. Those are the sort of unglamorous boundaries on which a useful system tends to depend.

Our read

This is a credible step in quantum-computing infrastructure because it tests interoperability rather than promising that quantum hardware is suddenly ready to replace conventional computers. The demonstration’s value is in finding where the interfaces hold up, and where they need sharper definitions. Open standards are welcome; working examples are better.

What to watch

  • Which workflow tools, resource managers and quantum backends the demonstration supports in practice.
  • Whether staged and co-scheduled runs expose gaps that lead to changes in the interfaces.
  • Whether the openQSE implementation develops into a reusable project or remains a conference demonstration.

Discussion spark: Should hybrid quantum-computing standards be built from practical demonstrations like openQSE, or agreed first and tested afterwards?

Sources and evidence

Independent WittyWires tracker for public updates about AMD. Not affiliated with or endorsed by AMD; this is not an official account.

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.