Prompted variable value arguments are stripped from `runbook run` command

[KennethBates]

The bug

When you run a runbook that has required prompted variables via the CLI, the defined --variable arguments in the command are stripped when building the automation command after a prompt.

Command to reproduce

octopus runbook run -p "ProjectName" -n "RunbookName" -s "SpaceName" -v "Name:Value" -e "EnvName"

Outcome

CLI output (strips away any defined variables in the same command)

octopus runbook run -p "New Project" -n "Runbook" -s "Kenny" -v "certCommonName:CLI" -v "prompt:CLI" -e "Development"
Runbook Runbook
Environments Development
Additional Options:
  Run At: Now
  Skipped Steps: None
  Guided Failure Mode: Use default setting from the target environment
  Package Download: Use cached packages (if available)
  Run Targets: All included
? Change additional options? Proceed to run

Automation Command: octopus runbook run --project 'New Project' --name 'Runbook' --environment 'Development' --no-prompt
Successfully started 1 runbook run(s)

Resulting run falls back to the prompted variables' default values.

Workaround

Specify the --no-prompt flag in the command. This preserves the configured variables in the command.

Versions

cli: 2.20.1

Octopus Server: 2026.2.1361

Links

Report: https://octopuscd.zendesk.com/agent/tickets/195639