Summary

When running coder create with the --yes flag, the CLI still prompts for parameter input instead of using default values or presets. This creates friction for automated workspace creation workflows.

Problem

Customers attempting to programmatically create workspaces using:

coder create ${WORKSPACE_NAME} \
  --template ${TEMPLATE_NAME} \
  --rich-parameter-file "${PARAM_FILE}" \
  --yes

Expect --yes to skip all interactive prompts and use defaults, but the CLI still waits for parameter input even when:

• All parameters have default values defined in the template
• A preset could be automatically selected

Expected Behavior

When --yes is provided, coder create should follow this precedence:

1. Use the default preset if one is defined in the template
2. Use default parameter values if no preset exists
3. Only require --rich-parameter-file or --parameter flags for parameters that have no default values
4. Never prompt for interactive input

Current Workaround

Users can explicitly specify a preset:

coder create ${_NAME} \
  --template ${TEMPLATE_NAME} \
  --preset ${PRESET_NAME} \
  --yes

Customer Impact

• Multiple customers have reported this issue
• Blocks automated workspace provisioning workflows
• Forces customers to use workarounds