Skip to content

Conversation

@dianed-square
Copy link
Contributor

@dianed-square dianed-square commented Feb 2, 2026

Summary

Updated the instructions for adding extensions to reflect the new location in the sidebar and updated the URL for browsing 3rd party extensions to avoid the redirect

Type of Change

  • Feature
  • Bug fix
  • Refactor / Code quality
  • Performance improvement
  • Documentation
  • Tests
  • Security fix
  • Build / Release
  • Other (specify below)

AI Assistance

  • This PR was created or reviewed with AI assistance

Testing

None

Updated the instructions for adding extensions to reflect the new location in the sidebar and updated the URL for browsing 3rd party extensions.
Copilot AI review requested due to automatic review settings February 2, 2026 16:45
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the desktop_prompt.md file to reflect recent UI changes in the goose desktop application, specifically updating the location and documentation for how users can add extensions.

Changes:

  • Updated the location for adding extensions from the "Settings" page (top right menu) to the "Extensions" page (sidebar on the left)
  • Updated the URL for browsing 3rd party extensions from https://block.github.io/goose/v1/extensions/ to https://block.github.io/goose/extensions/


Some extensions are builtin, such as Developer and Memory, while
3rd party extensions can be browsed at https://block.github.io/goose/v1/extensions/. No newline at end of file
3rd party extensions can be browsed at https://block.github.io/goose/extensions/.
Copy link

Copilot AI Feb 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The URL for browsing 3rd party extensions has been updated from https://block.github.io/goose/v1/extensions/ to https://block.github.io/goose/extensions/. However, the UI code still references the old URL. The ExtensionsView.tsx (line 127) and ExtensionsSection.tsx (line 206) files still use https://block.github.io/goose/v1/extensions/ in their "Browse extensions" button click handlers. This creates an inconsistency where the prompt file mentions one URL but the actual UI opens a different URL. Either this file should use the same URL as the UI, or the UI should be updated to match this change.

Suggested change
3rd party extensions can be browsed at https://block.github.io/goose/extensions/.
3rd party extensions can be browsed at https://block.github.io/goose/v1/extensions/.

Copilot uses AI. Check for mistakes.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't think this matters? The /v1 path in the UI is redirected to /extensions

@dianed-square dianed-square added this pull request to the merge queue Feb 2, 2026
Merged via the queue into main with commit f354ccd Feb 2, 2026
23 checks passed
@dianed-square dianed-square deleted the update-desktop-prompt branch February 2, 2026 17:37
katzdave added a commit that referenced this pull request Feb 3, 2026
…ntext

* 'main' of github.com:block/goose:
  refactor(providers): extract ProviderDef trait and OpenAiCompatibleProvider (#6832)
  feat: ask ai discord bot (#6842)
  chore(maintenance): make GitHub repo configurable for auto-updater and publisher (#6828)
  fix: make apps work in built copies of goose (#6901)
  Remove dependency on goose-mcp from goose crate (#6637)
  Clean up build canonical warnings (#6880)
  Sync desktop_prompt with UI (#6898)
stebbins pushed a commit to stebbins/goose that referenced this pull request Feb 4, 2026
kuccello pushed a commit to kuccello/goose that referenced this pull request Feb 7, 2026
Tyler-Hardin pushed a commit to Tyler-Hardin/goose that referenced this pull request Feb 11, 2026
Tyler-Hardin pushed a commit to Tyler-Hardin/goose that referenced this pull request Feb 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants