goose should scan recipes that a user wants to set up as scheduled to ensure it contains a prompt

[iandouglas]

Please explain the motivation behind the feature request.

A user reported that goose created a series of recipes for automation and gave goose times of day to run them, and they're well-written and well-formatted but lack a 'prompt' instruction in the YAML (it's generally considered to be an "optional" field).

goose then also built their ~/.local/share/goose/schedules.json for them, but nothing in the process checked that the recipes contained a 'prompt' so they COULD run as a scheduled recipe.

Describe the solution you'd like

For the UI, we should probably add something to the scheduler that scans the recipe to ensure it contains a prompt and any other validation on fields that are required in the recipe to be considered 'valid' for scheduling. If the recipe is missing anything, we should not allow scheduling the recipe and inform the user.

Since goose went ahead and wrote the schedules.json file for the user, goose should have some way of writing something into the session or logs that the recipe doesn't contain a 'prompt' so the user knows why the schedule isn't working.

Also, if the future needs of scheduling a recipe change, we should consider a way to re-scan existing recipes to ensure they still comply in case a future change doesn't allow for backward-compatibility.

Describe alternatives you've considered

n/a

Additional context

n/a

• I have verified this does not duplicate an existing feature request

[screwgauge77]

.take

[github-actions[bot]]

Thanks for taking this issue! Let us know if you have any questions!

[taniandjerry]

Let us know how progress is going, and if you need any help here as it relates to #5045, @screwgauge77 !

[DOsinga]

the real solution here is to have the recipe that is executed also take into account the instructions. then you can default the prompt to do the thing /cc @Kvadratni @tlongwell-block

[Kvadratni]

yup agreed 100%

[iandouglas]

if !prompt && instructions && headless_mode:
  prompt = 'follow the instructions'

there, i fixed it ;)

[tlongwell-block]

We (effectively) do this for subagents already. Can definitely incorporate it into recipe execution.

Will be moving the scheduler to use the unified execution path as part of #4389 right after subrecipes is done (in progress now), so we can standardize this behavior across all recipe executions

[taniandjerry]

So just to confirm, is this issue then still open to any contributions or something to close? :O

[iandouglas]

@taniandjerry yeah I think this is mostly about discussion, but the changes are being worked on from the looks of it.

[taniandjerry]

thank you! converted this to a discussion so that updates and anything else can be shared & referenced here :)

[amed-xyz]

I believe this was addressed here #5359. Would love to hear your thoughts!