Centralized configuration for corporate environments for Goose Desktop #4624
-
|
In corporate environments, there may be concerns about allowing users to install arbitrary extensions (or even using the pre-installed ones such as computer-use). Are there any thoughts around features for allowing corporate IT to manage goose (desktop) configuration? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
@dcieslak19973 yes - for sure. ourselves, we use the ALLOWLIST feature, and goose is packaged with that setup so it looks up a list of allowed extensions when someone tries to install one (and this is distributed via a managed software update center). not a trivial amount of work but pretty simple (could be better I am sure). really it has to be down to packaging up the .app or whatever format for the desktop environment you need so when people get it, it knows about that (either allowlist or perhaps something new and bespoke, or even hard coded into it in the build process). This isn't just for desktop extensions, but increasingly remote MCP servers (as they are effectively injecting prompts and tool calls) that you would want to do this for. |
Beta Was this translation helpful? Give feedback.
@dcieslak19973 yes - for sure. ourselves, we use the ALLOWLIST feature, and goose is packaged with that setup so it looks up a list of allowed extensions when someone tries to install one (and this is distributed via a managed software update center). not a trivial amount of work but pretty simple (could be better I am sure).
really it has to be down to packaging up the .app or whatever format for the desktop environment you need so when people get it, it knows about that (either allowlist or perhaps something new and bespoke, or even hard coded into it in the build process). This isn't just for desktop extensions, but increasingly remote MCP servers (as they are effectively injecting pro…