fix: register goose:// scheme handler in Flatpak desktop entry - #10461
Merged
Conversation
The Flatpak build's generated .desktop file has no MimeType entry, so the
host OS never registers Goose as the handler for goose:// URLs and the
extension-page install buttons do nothing when installed via Flatpak. The
runtime setAsDefaultProtocolClient('goose') call cannot register a handler
from inside the sandbox; the exported desktop entry is the only
registration path.
Set mimeType in the maker-flatpak options so the installer's desktop
template emits MimeType=x-scheme-handler/goose;, matching the entry the
deb/rpm desktop templates already ship.
Fixes aaif-goose#10441
Co-Authored-By: Claude <noreply@anthropic.com>
Abhijay007
reviewed
Jul 14, 2026
Abhijay007
approved these changes
Jul 14, 2026
Co-Authored-By: Claude <noreply@anthropic.com>
alexhancock
approved these changes
Jul 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #10441
The Flatpak build's generated desktop entry has no
MimeType, so the hostOS never registers Goose as the handler for
goose://URLs and theextension-page install buttons do nothing when installed via Flatpak. The
runtime
setAsDefaultProtocolClient('goose')call cannot register a handlerfrom inside the sandbox — the exported desktop entry is the only
registration path, and the deb/rpm builds already ship it via their
desktopTemplatefiles.Fix: set
mimeType: ['x-scheme-handler/goose']in the maker-flatpak optionsin
ui/desktop/forge.config.ts. The flatpak installer's desktop templateemits
MimeType=x-scheme-handler/goose;from this option, matching thedeb/rpm entries.
Testing
@electron-forge/maker-flatpak@7.11.1passes this option throughto
@malept/electron-installer-flatpak, and rendered that installer'sdesktop template with this config to confirm the generated entry gains the
MimeTypeline (identical to the deb/rpm entries).fork — both variants built and packaged the Flatpak successfully:
https://github.com/AgarwalManas/goose/actions/runs/29342667698
Flatpak install.
Related Issues
Relates to #10441
Screenshots/Demos (for UX changes)
N/A — packaging config change only; no UX change.