Downloaded extensions don't work in Goose Desktop for Windows

[understood-the-assignment]

Describe the bug

You can download extensions for Goose for Windows, but Goose isn't able to actually load them.

To Reproduce
Steps to reproduce the behavior:

1. Click "Browse Extensions"
2. Find an extension you like
3. Click "Install"
4. Click "OK"
5. See error

Expected behavior
Extensions should load

Screenshots

Please provide following information:

• OS & Arch: Windows 11
• Interface: UI
• Version: 1.3.0
• Extensions enabled: Any
• Provider & Model: N/A

Additional context
The error (when you click "Copy Error") is:

Error activating extension: Node.js installer script not found

[rromanw]

Bump, any ideas what to do ?

[milllan]

still not working for me :(

[DOsinga]

can you copy the error when this pops up and share here?

[understood-the-assignment]

@DOsinga This was already done, you can find it at the bottom of the issue description above. That's the entire contents of the copied error.

[DOsinga]

Error activating extension: Node.js installer script not found

I see. well, that's no good.

[vlascik]

The whole idea with node.js installer is not great and doesn't really work.

I have a fix in the making at least for cases where node.js is installed, but not in the default Program files folder (it tries to read the node path from registry instead), but the whole Windows situation is bad - the builds are constantly broken, extensions do not work, node MCPs don't work, etc.

Good Windows support is going to need a lot more automated testing infrastructure.

Anyway, in the meantime, I will try to post a few fixes in next few days.

[DOsinga]

unfortunately you are right, the key issue is that we do not have anybody on the core team that uses windows on a day to day basis

[vlascik]

@DOsinga Yeah, figured out that much :) Given that there's still about as many developers on Windows as there are on Mac + Linux combined, not to mention the end-user ratios, that's probably not a great situation...

Btw. there is a way to run Windows in docker containers, so maybe at least some tests could be set up? At least verifying that the app builds, starts, and can perform some basic functions.

Anyway, tried to mitigate this particular issue in #5233. Hope it solves it for most people, and can guide the rest towards fixing it on their own.

[DOsinga]

really appreciate your work on this @vlascik

[mattcrichards]

I am having this very same issue, and interestingly on my first session wherein I first enabled extensions, it worked great. I then downloaded a goose update, quit the app, launched the update and neither extension I had previously enabled (voice and vs code) was able to start. I went back to the previous version and it didn't work there either.

Interesting though that it worked on the very first run.