Fix: Recipe Extensions Not Loading in Desktop #6777

zanesq · 2026-01-28T17:32:01Z

Summary: Fix desktop recipes not using default extensions

Problem

Recipes with an empty extensions: [] array would cause resolve_extensions_for_new_session
to return no extensions, instead of falling back to the user's default enabled extensions.

Solution

Strip empty extension arrays in the frontend before saving/running recipes.

Files Changed

ui/desktop/src/recipe/index.ts

Added stripEmptyExtensions() utility function that removes the extensions property
if it's an empty array

ui/desktop/src/components/recipes/RecipesView.tsx

handleStartRecipeChat(): Strip empty extensions in memory before running a recipe
Removed unused recipeId parameter

ui/desktop/src/components/recipes/CreateEditRecipeModal.tsx

getCurrentRecipe(): Use stripEmptyExtensions() when building recipe to save

ui/desktop/src/components/recipes/CreateRecipeFromSessionModal.tsx

handleCreateRecipe(): Simply don't set extensions at all (instead of setting [])

ui/desktop/src/components/schedule/ScheduleModal.tsx

recipeToYaml(): Strip empty extensions before converting recipe to YAML for scheduling

How it works

If a recipe has extensions: [], it gets stripped to extensions: undefined
Backend's resolve_extensions_for_new_session(None, override_extensions) then falls
through to use the UI's enabled extensions (desktop) or get_enabled_extensions() (scheduler)

…ensions * 'main' of github.com:block/goose: chore: re-sync package-lock.json (#6783) upgrade electron to 39.3.0 (#6779) allow skipping providers in test_providers.sh (#6778) fix: enable custom model entry for OpenRouter provider (#6761) Remove codex skills flag support (#6775) Improve mcp test (#6671) Feat/anthropic custom headers (#6774) Fix/GitHub copilot error handling 5845 (#6771) fix(ui): respect width parameter in MCP app size-changed notifications (#6376) fix: address compilation issue in main (#6776)

Copilot

Pull request overview

Fixes goose Desktop sessions started from recipes to correctly include the UI-enabled extensions by merging recipe-specified extensions with the per-session extension overrides instead of letting recipe extensions fully replace UI overrides.

Changes:

Initialize new sessions’ enabled extensions from extension_overrides (UI settings) and then merge in any recipe-required extensions not already present by name.
Ensures recipe-required extensions are added while preserving the UI-selected extension config when names overlap.

crates/goose-server/src/routes/agent.rs

DOsinga · 2026-01-28T21:02:21Z

I still don't understand the issue. this seems to be like the correct behavior. if the recipe specifies extensions, we should use those. if the recipe specifies an empty list, we should run with no extensions. if a recipe does not specify extensions, then we should use the one that the system has. /cc @lifeizhou-ap

angiejones · 2026-01-28T21:20:13Z

if a recipe does not specify extensions, then we should use the one that the system has. /cc @lifeizhou-ap

but it's not using the ones the system has. it loads as 0 extensions enabled and then is unable to run

zanesq · 2026-01-28T21:35:47Z

I discussed it with @DOsinga gonna take a different approach and handle it in the desktop code. The main issue is desktop is writing an empty extensions array rather than no extensions.

lifeizhou-ap · 2026-01-29T00:17:18Z

I discussed it with @DOsinga gonna take a different approach and handle it in the desktop code. The main issue is desktop is writing an empty extensions array rather than no extensions.

Yes! I noticed this late yesterday when testing the sub recipe feature. When user creates recipe via UI it includes "extensions: []" in the file. Previously it does not matter in Desktop because Desktop ignores the extensions in the recipe. Since we unified the recipe extension behaviour in Desktop, CLI and Scheduler recently, Desktop user has different experiences now. I was about fixing this today. Thanks @zanesq for fixing this

DOsinga

can do with some cleaning of LLM comments

DOsinga · 2026-01-28T23:24:23Z

ui/desktop/src/recipe/index.ts

+ * This ensures recipes without explicit extensions will use the default enabled extensions
+ * from the user's config in the desktop rather than loading with no extensions.
+ */
+export function stripEmptyExtensions<T extends { extensions?: unknown[] | null }>(recipe: T): T {


why this complicated type? shouldn't this just be Recipe in, Recipe out? that would save us some casting above too

DOsinga · 2026-01-29T01:23:47Z

ui/desktop/src/components/schedule/ScheduleModal.tsx

 }

 function recipeToYaml(recipe: Recipe): string {
+  // Strip empty extensions to ensure scheduled recipes use default enabled extensions


hmm, we discussed this, that's not how the scheduler works

Yes, scheduler always respect the extension config in recipe, not like Desktop. Maybe we should not apply this stripEmptyExtensions here.

DOsinga · 2026-01-29T01:24:26Z

ui/desktop/src/components/schedule/ScheduleModal.tsx


-  if (recipe.extensions && recipe.extensions.length > 0) {
-    cleanRecipe.extensions = recipe.extensions.map((ext) => {
+  if (processedRecipe.extensions && processedRecipe.extensions.length > 0) {


and we're stripping it anyway here, so this feels like a no op

DOsinga · 2026-01-29T01:25:02Z

ui/desktop/src/components/recipes/CreateRecipeFromSessionModal.tsx

    setIsCreating(true);
    try {
      // Create the recipe object from form data
+      // Don't set extensions - let the recipe use default enabled extensions


typical LLM comment

DOsinga · 2026-01-29T01:29:27Z

ui/desktop/src/components/recipes/CreateEditRecipeModal.tsx

+    ) as ExtensionConfig[];
+
+    // Use stripEmptyExtensions to avoid saving empty extensions array
+    // Empty extensions array would prevent default extensions from loading


do we? we do want to make the distinction between empty lists and no recipes. if you now load a recipe that pre-existed and had an empty list of extensions, and you save it, it now has no extensions.

you want to make sure that if we create a recipe the default extensions are undefined and then respect whatever it said already

lifeizhou-ap · 2026-01-29T02:32:42Z

ui/desktop/src/components/recipes/CreateEditRecipeModal.tsx

-      return recipe.extensions;
-    }
-    return [];
+  const [recipeExtensions] = useState<ExtensionConfig[] | undefined>(() => {


That's great! I was about suggesting this too! You are quick :)

* 'main' of github.com:block/goose: (62 commits) Swap canonical model from openrouter to models.dev (#6625) Hook thinking status (#6815) Fetch new skills hourly (#6814) copilot instructions: Update "No prerelease docs" instruction (#6795) refactor: centralize audience filtering before providers receive messages (#6728) update doc to remind contributors to activate hermit and document minimal npm and node version (#6727) nit: don't spit out compaction when in term mode as it fills up the screen (#6799) fix: correct tool support detection in Tetrate provider model fetching (#6808) Session manager fixes (#6809) fix(desktop): handle quoted paths with spaces in extension commands (#6430) fix: we can default gooseignore without writing it out (#6802) fix broken link (#6810) docs: add Beads MCP extension tutorial (#6792) feat(goose): add support for AWS_BEARER_TOKEN_BEDROCK environment variable (#6739) [docs] Add OSS Skills Marketplace (#6752) feat: make skills available in codemode (#6763) Fix: Recipe Extensions Not Loading in Desktop (#6777) Different approach to determining final confidence level of prompt injection evaluation outcomes (#6729) fix: read_resource_tool deadlock causing test_compaction to hang (#6737) Upgrade error handling (#6747) ...

…sion-session * 'main' of github.com:block/goose: (78 commits) copilot instructions: Update "No prerelease docs" instruction (#6795) refactor: centralize audience filtering before providers receive messages (#6728) update doc to remind contributors to activate hermit and document minimal npm and node version (#6727) nit: don't spit out compaction when in term mode as it fills up the screen (#6799) fix: correct tool support detection in Tetrate provider model fetching (#6808) Session manager fixes (#6809) fix(desktop): handle quoted paths with spaces in extension commands (#6430) fix: we can default gooseignore without writing it out (#6802) fix broken link (#6810) docs: add Beads MCP extension tutorial (#6792) feat(goose): add support for AWS_BEARER_TOKEN_BEDROCK environment variable (#6739) [docs] Add OSS Skills Marketplace (#6752) feat: make skills available in codemode (#6763) Fix: Recipe Extensions Not Loading in Desktop (#6777) Different approach to determining final confidence level of prompt injection evaluation outcomes (#6729) fix: read_resource_tool deadlock causing test_compaction to hang (#6737) Upgrade error handling (#6747) Fix/filter audience 6703 local (#6773) chore: re-sync package-lock.json (#6783) upgrade electron to 39.3.0 (#6779) ...

use UI enabled extensions in recipes also

ce09fd9

zanesq requested review from DOsinga and alexhancock January 28, 2026 17:32

angiejones requested a review from Copilot January 28, 2026 20:53

Copilot started reviewing on behalf of angiejones January 28, 2026 20:54 View session

Copilot AI reviewed Jan 28, 2026

View reviewed changes

crates/goose-server/src/routes/agent.rs Outdated Show resolved Hide resolved

strip empty extensions when saving and loading recipes

68732d8

DOsinga approved these changes Jan 29, 2026

View reviewed changes

cleanup

632653e

lifeizhou-ap reviewed Jan 29, 2026

View reviewed changes

lifeizhou-ap approved these changes Jan 29, 2026

View reviewed changes

zanesq merged commit c8b02e0 into main Jan 29, 2026
18 checks passed

zanesq deleted the zane/ui-recipe-extensions branch January 29, 2026 02:39

This was referenced Jan 29, 2026

chore(release): release version 1.22.0 (minor) #6812

Closed

chore(release): release version 1.22.0 (minor) #6813

Open

Fix: Recipe Extensions Not Loading in Desktop #6777

Fix: Recipe Extensions Not Loading in Desktop #6777

Uh oh!

Conversation

zanesq commented Jan 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary: Fix desktop recipes not using default extensions

Problem

Solution

Files Changed

How it works

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

DOsinga commented Jan 28, 2026

Uh oh!

angiejones commented Jan 28, 2026

Uh oh!

zanesq commented Jan 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

lifeizhou-ap commented Jan 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

DOsinga left a comment

Choose a reason for hiding this comment

Uh oh!

DOsinga Jan 28, 2026

Choose a reason for hiding this comment

Uh oh!

DOsinga Jan 29, 2026

Choose a reason for hiding this comment

Uh oh!

lifeizhou-ap Jan 29, 2026

Choose a reason for hiding this comment

Uh oh!

DOsinga Jan 29, 2026

Choose a reason for hiding this comment

Uh oh!

DOsinga Jan 29, 2026

Choose a reason for hiding this comment

Uh oh!

DOsinga Jan 29, 2026

Choose a reason for hiding this comment

Uh oh!

lifeizhou-ap Jan 29, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

zanesq commented Jan 28, 2026 •

edited

Loading

zanesq commented Jan 28, 2026 •

edited

Loading

lifeizhou-ap commented Jan 29, 2026 •

edited

Loading