Please explain the motivation behind the feature request.
Currently if I start a Goose CLI session using a recipe (e.g. goose run --interactive --recipe recipe.yaml) where recipe.yaml defines a certain extension, if I exit that session then later resume with --resume and --name/--path I'd expect the resumed session to include the same extensions as the original session (that are defined in the recipe). But it seems like dynamic extensions are enabled in memory and don't get saved to the session, so they aren't loaded when resuming that session

Describe the solution you'd like
I'd like to be able to define a recipe recipe.yaml which includes an extension like mcp_pagerduty then start a session using the recipe: goose run --interactive --recipe recipe.yaml. If I later exit the session, I'd like to be able to goose session --resume --name <session_id>.jsonl and have the new(resumed) session auto load mcp_pagerduty like the original recipe session did

Describe alternatives you've considered
Since I've enabled mcp_pagerduty as a global extension I can ask the model to enable it dynamically in the session, but it would be a more consistent user experience for resumed recipe sessions to auto load all the same extensions defined in the recipe file

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