Skip to main content
pick_changes finds the latest release, asks which ref to start from, and lists the commits since the answer.

Set up the ask step

The pick step’s input sets the question and its answer:
  • prompt is the question.
  • outputSchema lists the fields to fill in. Each field’s description is what the person reads for it.
  • default is the answer to use when nobody answers, here the latest release’s tag.
  • whenUnanswered: default uses default instead of failing the run.
Later steps read the answer as {{pick.answer.base}}.

Answer in the terminal

The question appears on stderr. Type an answer and press Enter:

When nobody answers

With no terminal to ask, as in a script or a scheduled job, the step uses default:
A blank answer in the terminal declines the question and gives the same result.

Branch with route

Take different steps depending on the answer.

Run a plan

Pass inputs on the command line instead.

Serve plans over MCP

Ask the question through an MCP client.

Debug a plan

Run the plan in the workbench, where questions appear as a form.