Why is STM32CubeCLI released as a beta?

STM32CubeCLI has run inside STM32CubeIDE for Visual Studio Code since April 2025 and inside STM32CubeMX2 since March 2026, on top of five years of internal use before either of those. The wrapper, the bundle manager, and the bundle format are neither new nor experimental.

What’s still settling is the command surface — the exact names and shape of the commands you type. Today, cube commands are named after the underlying tool ( cube cmake, cube programmer, cube mx), not after the task. Whether the CLI grows task-level commands instead (for example a single cube build or cube flash) is still an open decision.

This documentation portal is built for continuous deployment — new chapters and fixes ship as real feedback comes in, rather than waiting for everything to be finished up front.

What this means for you

• The tools you rely on are stable. Reliability isn’t the open question.

• Exact command names may change before general availability. A script or CI pipeline that calls a specific command today may need a small update later if that command is renamed or reorganized.

• Your project’s pinned tool versions aren’t affected. The manifest and lock file mechanism — what makes builds reproducible — isn’t part of what’s changing.

• Missing something, or found an issue? Tell us.

See the Command reference for the current command surface, and the release notes for anything that changes between releases.

Have a question, a request, or found an issue? Ask on the ST community forum.