Add ability to specify model in recipe

[ianreay]

Please explain the motivation behind the feature request. Different tasks need different models. Sometimes you want expensive reasoning models. Sometimes you want light weight workhorse models. Configuring these as the global level makes it very hard to use multiple models concurrently for multiple tasks.

Describe the solution you'd like Allow a recipe to optionally include the model configuration that should be used.

Describe alternatives you've considered Right now I manually change between models but this is very tedious.

Additional context I can provide more details if necessary.

This request is similar too https://github.com/block/goose/issues/2435 but having this in the recipe would be very valuable to make re-usable across teams.

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

[aharvard]

I think this feature would be beneficial and I would use.

[DOsinga]

we have a settings section now in recipes that allows you to do this:

#[derive(Serialize, Deserialize, Debug, Clone, ToSchema)] pub struct Settings { #[serde(skip_serializing_if = "Option::is_none")] pub goose_provider: Option<String>,

#[serde(skip_serializing_if = "Option::is_none")]
pub goose_model: Option<String>,

#[serde(skip_serializing_if = "Option::is_none")]
pub temperature: Option<f32>,

@blackgirlbytes - we should add this to the documentation though