goose
goose copied to clipboard
JetBrains listed as built-in extension in crates/goose-cli/src/commands/configure.rs
Describe the bug
Enabling the JetBrains extension through goose configure fails because the JetBrains extension is incorrectly listed as a built-in option in Goose. Attempting to activate it results in the following error:
Error activating extension: Failed to add extension configuration, error: ProcessExit(ProcessExit { stderr: " \u{1b}[2m2025-11-06T00:32:11.901604Z\u{1b}[0m \u{1b}[32m INFO\u{1b}[0m \u{1b}[1;32mgoose_mcp::mcp_server_runner\u{1b}[0m\u{1b}[32m: \u{1b}[32mStarting MCP server\u{1b}[0m\n \u{1b}[2;3mat\u{1b}[0m crates/goose-mcp/src/mcp_server_runner.rs:18\n\n \u{1b}[2m2025-11-06T00:32:11.901628Z\u{1b}[0m \u{1b}[33m WARN\u{1b}[0m \u{1b}[1;33mgoose_mcp::mcp_server_runner\u{1b}[0m\u{1b}[33m: \u{1b}[33mUnknown MCP server name: jetbrains\u{1b}[0m\n \u{1b}[2;3mat\u{1b}[0m crates/goose-mcp/src/mcp_server_runner.rs:27\n\nError: Unknown MCP server name: jetbrains\n", source: ConnectionClosed("initialize response") })
The issue seems to be that the JetBrains extension is still listed in as a built-in extension in goose configure despite being removed in PR #2589.
The JetBrains extension appears in the CLI configuration dialog at:
But is not present in:
crates/goose-mcp/src/mcp_server_runner.rs(the source of truth for built-in extensions)ui/desktop/src/components/settings/extensions/bundled-extensions.json(Desktop UI list)
To Reproduce Steps to reproduce the behavior:
- Run
goose configurein the CLI. - Select "Add Extension" > "Built-in Extension".
- Enable the JetBrains extension from the list.
- Open goose Desktop and start a new session. Get error
Expected behavior The JetBrains extension should not appear in the list of built-in extensions if it is unsupported
Please provide the following information
- OS & Arch: macOS
- Interface: UI (error)
- Version: 1.12.1
- Extensions enabled: Developer, Todo, Extension Manager
- Provider & Model: n/a