New feature
The Seqera API supports the launchContainer field, but this is not exposed in the nextflow launch CLI. It's important to be able to control the Nextflow version so it matches your local version.
Use case
If my remote Nextflow uses 25.04 by default but my local version uses 25.10, I may wish to select the launchContainer as myregistry.io/nextflow:25.10.4
Suggested implementation
nextflow launch -launch-container myregistry.io/nextflow:25.10.4
Default is null and ignored in the POST request.