riot run

riot run is the command that turns a built package into something you can actually use.

The simplest form looks like:

riot run hello

That is important because it means the common execution path is package-oriented, not a pile of manually constructed _build paths.

Why riot run matters

If build output is hard to execute, the toolchain has only solved half the problem.

riot run makes execution part of the product by handling:

• package-aware entrypoint selection
• the normal local workflow for binaries
• a stable command surface that can appear in docs, editors, and scripts

The normal place in the loop

Most users hit riot run after:

1. editing source files
2. validating with riot check or riot build
3. wanting to exercise the resulting binary immediately

That makes riot run one of the most important commands in the whole toolchain story.

What good riot run usage looks like

Good use of riot run tends to be:

• explicit about which package or binary is being run
• close to the build/test loop
• the same in local development and docs examples

That consistency is valuable. It means examples in the docs can mirror what users should really do.

Another angle on the same command

This page treats riot run as part of the day-to-day toolchain loop.

There is also a package-manager angle to the same command, especially when resolution or installation behavior matters. Read Package Manager / riot run for that view.