{"schema_version":1,"generated_at":"2026-10-26T10:18:14Z","issues_generated_at":"2026-10-26T10:12:02Z","lookback_days":45,"license_note":"Issue metadata from public GitHub repos.","harness":"goose","issues":[{"id":"aaif-goose/goose#12703","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12703,"title":"Render A2UI embedded resources from MCP tool results in goose desktop","url":"https://github.com/aaif-goose/goose/issues/12703","state":"open","state_reason":null,"labels":[],"created":"2026-10-06T01:30:18Z","updated":"2026-10-22T22:04:35Z","closed":null,"reactions":0,"thumbs_up":0,"comments":15,"severity":"medium","severity_reasons":["engagement 15","class:mcp/tools"],"topic":"mcp/tools","classes":["mcp/tools","self-host/headless","install/update","crash/hang"],"cosmetic_ui":false,"summary":"Proposal: goose doesn't support A2UI today. This issue proposes adding it to goose desktop, starting with rendering A2UI surfaces returned by MCP servers. The first version would be off by default and limited to the A2UI basic catalog…","versions":[],"error_snippets":["capabilities.extensions","call (name, surfaceId, sourceComponentId, context) would go through the existing","path to the extension that produced the surface. That path requires a tool visible to apps (the default when","ExtensionManager::dispatch_tool_call","A2UI would render in goose's own window, not a sandbox, so goose would treat every payload as untrusted data:"],"workaround":null,"fixed_in":null,"score":91.5,"first_seen":"2026-10-26T10:12:02Z"},{"id":"aaif-goose/goose#12068","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12068,"title":"Support SEP-2640 Skills Extension (skills over MCP) as host","url":"https://github.com/aaif-goose/goose/issues/12068","state":"open","state_reason":null,"labels":[],"created":"2026-09-14T21:17:52Z","updated":"2026-10-19T18:55:00Z","closed":null,"reactions":1,"thumbs_up":1,"comments":13,"severity":"medium","severity_reasons":["class:mcp/tools"],"topic":"mcp/tools","classes":["mcp/tools","self-host/headless","install/update","crash/hang"],"cosmetic_ui":false,"summary":"What problem would this solve? MCP has no standard way to ship workflow instructions alongside the tools they describe. Server instructions are size-bounded, so complex workflows do not fit. Today a server and the skill that teaches how to…","versions":[],"error_snippets":["MCP has no standard way to ship workflow instructions alongside the tools they describe. Server instructions are size-bounded, so complex workflows do not fit. Today a server and the skill that teaches how to use it are ","SEP-2640 (io.modelcontextprotocol/skills, modelcontextprotocol/modelcontextprotocol#2640, merged) fixes this by serving Agent Skills over MCP Resources: skill:// URIs plus skills/list, skills/get, and optional resources/","Goose as host supports the Skills Extension:"],"workaround":null,"fixed_in":null,"score":75.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#12805","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12805,"title":"Define an OS sandbox boundary for shell and tool subprocesses","url":"https://github.com/aaif-goose/goose/issues/12805","state":"open","state_reason":null,"labels":[],"created":"2026-10-09T21:41:38Z","updated":"2026-10-26T07:37:31Z","closed":null,"reactions":2,"thumbs_up":1,"comments":2,"severity":"medium","severity_reasons":["class:network"],"topic":"network","classes":["network","self-host/headless","mcp/tools"],"cosmetic_ui":false,"summary":"What problem would this solve? goose can already ask before a tool runs (approve, smartapprove) and can deny a tool entirely. That is a permission policy, not a sandbox. Once a command, MCP server, or extension subprocess is allowed, it…","versions":["1.25.0"],"error_snippets":["tool executes the model-supplied command with no OS boundary. The default","excludedCommands",") and a removed Seatbelt experiment ([michaelneale/agent-seatbelt-sandbox](https://github.com/michaelneale/agent-seatbelt-sandbox), which @michaelneale has been using as the macOS reference: kernel","sandbox-exec","Who this affects: anyone running goose on a machine that has credentials, other projects, or network access they do not want an agent session to touch. It also blocks a safer default than \"ask every time\" or \"allow the w"],"workaround":null,"fixed_in":null,"score":71.8,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#12905","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12905,"title":"OAuth succeeds, then the extension fails, when the token exceeds Windows Credential Manager's 2560-char limit","url":"https://github.com/aaif-goose/goose/issues/12905","state":"open","state_reason":null,"labels":[],"created":"2026-10-15T00:49:26Z","updated":"2026-10-26T02:39:22Z","closed":null,"reactions":0,"thumbs_up":0,"comments":4,"severity":"critical","severity_reasons":["title:data-loss/security"],"topic":"auth/session","classes":["auth/session","self-host/headless","mcp/tools"],"cosmetic_ui":false,"summary":"Describe the bug: On Windows, a remote MCP extension fails to load after a successful authorization. The browser shows Goose's own \"Authorization Success\" page, then the extension errors. The real cause is that saving the credential fails…","versions":["1.54","1.53"],"error_snippets":["On Windows, a remote MCP extension fails to load after a successful authorization. The browser shows Goose's own \"Authorization Success\" page, then the extension errors. The real cause is that saving the credential fails","WARN [OAuth: ] Browser authorization flow failed: Internal error:","Failed to save credentials: Failed to access keyring:","Attribute 'password encoded as UTF-16' is longer than platform limit of 2560 chars","WARN Failed to load extension : failed to initialize MCP client:"],"workaround":{"text":"Additional context: GOOSE_DISABLE_KEYRING=1 is a complete workaround, which confirms the diagnosis.","source":"issue body","url":"https://github.com/aaif-goose/goose/issues/12905"},"fixed_in":null,"score":71.0,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#11740","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":11740,"title":"feat(tasks): unified task registry + tasks platform extension (background processes, timers, wait_for wake-ups)","url":"https://github.com/aaif-goose/goose/issues/11740","state":"open","state_reason":null,"labels":[],"created":"2026-09-01T05:02:56Z","updated":"2026-10-09T09:43:21Z","closed":null,"reactions":2,"thumbs_up":2,"comments":5,"severity":"medium","severity_reasons":["class:always-on/daemon","class:network"],"topic":"always-on/daemon","classes":["always-on/daemon","network","self-host/headless","mcp/tools"],"cosmetic_ui":false,"summary":"Long-running work is a first-class citizen in agent-driven development — builds, test suites, dev servers, watchers, interactive programs (debuggers, REPLs), and scheduled follow-ups. Today goose has no first-class way to run that work in…","versions":[],"error_snippets":["), no cancel-with-partial-output, no structured lifecycle — every ad-hoc","enum should reserve the full space (","), platform extension with the six tools above (","A unified **task registry** in the agent runtime, with a small platform extension exposing it to the model:"],"workaround":null,"fixed_in":null,"score":69.8,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#10839","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":10839,"title":"Support MCP's server.json and mcp.json import","url":"https://github.com/aaif-goose/goose/issues/10839","state":"open","state_reason":null,"labels":[],"created":"2026-07-31T09:14:48Z","updated":"2026-10-14T21:06:30Z","closed":null,"reactions":2,"thumbs_up":2,"comments":6,"severity":"medium","severity_reasons":["class:self-host/headless","class:mcp/tools"],"topic":"self-host/headless","classes":["self-host/headless","mcp/tools"],"cosmetic_ui":false,"summary":"goose has its own repository for MCP servers but given that there is an MCP server for everything now, this concept is outdated. goose has deeplinks to install remote MCP servers but uses its own format for that. Meanwhile the world has…","versions":[],"error_snippets":[],"workaround":null,"fixed_in":null,"score":65.8,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#13011","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":13011,"title":"Desktop (Windows, 1.53.0): turn-final assistant messages ([thinking + text], no tool call) missing from chat view, while fully stored and re-played by the server","url":"https://github.com/aaif-goose/goose/issues/13011","state":"open","state_reason":null,"labels":[],"created":"2026-10-19T23:40:55Z","updated":"2026-10-23T00:30:40Z","closed":null,"reactions":0,"thumbs_up":0,"comments":2,"severity":"medium","severity_reasons":["class:self-host/headless","class:mcp/tools"],"topic":"self-host/headless","classes":["self-host/headless","mcp/tools","auth/session"],"cosmetic_ui":false,"summary":"Desktop (Windows, 1.53.0): turn-final assistant messages ([thinking + text], no tool call) missing from chat view, while fully stored and re-played by the server Goose Desktop 1.53.0, Windows 11 Pro; provider ollamacloud Models…","versions":["1.53.0","5.3-flash","1.51"],"error_snippets":["(551 message rows),","In tool-loop turns the chat view shows the expanded thinking block, tool requests and tool output — then the turn visually ends. The turn-final assistant message (content `[thinking + text]`, **no trailing toolRequest**)","Observed correlation (small sample — observed, not established): **both** invisible messages are `[thinking + text]` with **no** trailing toolRequest, while every intermediate message that did render carried a toolReques","1. **Model/provider never failed.** `usage_ledger` for `20261019_5`: 235 requests, 0 with `output_tokens < 40`; no error entries for LLM traffic in serve logs.","2. **The message streamed fully (18002).** `llm_request.N.jsonl` shows that request as 867 streamed deltas ending in a finalize usage record (output 2,093 tokens). The 22:59 UTC 17901 roll was already overwritten before "],"workaround":null,"fixed_in":null,"score":63.2,"first_seen":"2026-10-20T09:28:14Z"},{"id":"aaif-goose/goose#13022","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":13022,"title":"Add harness-level progressive MCP tool discovery","url":"https://github.com/aaif-goose/goose/issues/13022","state":"open","state_reason":null,"labels":[],"created":"2026-10-20T13:52:05Z","updated":"2026-10-21T00:48:32Z","closed":null,"reactions":0,"thumbs_up":0,"comments":3,"severity":"medium","severity_reasons":["class:mcp/tools"],"topic":"mcp/tools","classes":["mcp/tools","self-host/headless","network"],"cosmetic_ui":false,"summary":"Add harness-level progressive tool discovery so Goose can keep most MCP tool schemas out of the model context until they are relevant. A small always-visible discovery tool could search across configured MCP servers using server/tool…","versions":[],"error_snippets":["A small always-visible discovery tool could search across configured MCP servers using server/tool hints, activate matching tools for the session, and refresh the model-visible catalog. MCP servers that support dynamic c","Large MCPs (GitHub, Google Drive, etc.) can create tool-schema explosion. Buzz has the same issue: Buzz PR #1329 marks tools as always-loaded or search-loaded for harnesses that support deferred tools, but Goose currentl","Related: #10955 (progressive extension activation for external harnesses)."],"workaround":null,"fixed_in":null,"score":61.9,"first_seen":"2026-10-26T10:12:02Z"},{"id":"aaif-goose/goose#13128","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":13128,"title":"Goose APP UPDATE BUG","url":"https://github.com/aaif-goose/goose/issues/13128","state":"open","state_reason":null,"labels":[],"created":"2026-10-25T04:01:14Z","updated":"2026-10-25T23:56:59Z","closed":null,"reactions":0,"thumbs_up":0,"comments":1,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"Describe the bug 💡 Before filing, please check common issues: https://goose-docs.ai/docs/troubleshooting 📦 To help us debug faster, attach your diagnostics zip if possible. 👉 How to capture it…","versions":["1.0.2"],"error_snippets":["4. See error","A clear and concise description of what you expected to happen.","If applicable, add screenshots to help explain your problem."],"workaround":null,"fixed_in":null,"score":59.5,"first_seen":"2026-10-25T09:11:37Z"},{"id":"aaif-goose/goose#11323","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":11323,"title":"ACP desktop drops CallToolResult._meta before MCP App notification","url":"https://github.com/aaif-goose/goose/issues/11323","state":"open","state_reason":null,"labels":[],"created":"2026-08-18T13:44:38Z","updated":"2026-10-19T17:06:34Z","closed":null,"reactions":1,"thumbs_up":1,"comments":7,"severity":"medium","severity_reasons":["class:mcp/tools"],"topic":"mcp/tools","classes":["mcp/tools","self-host/headless","install/update"],"cosmetic_ui":false,"summary":"Describe the bug Goose Desktop's ACP chat path drops the MCP server's non-routing CallToolResult.meta before delivering ui/notifications/tool-result to an MCP App. The app receives content and structuredContent, but meta is reconstructed…","versions":["1.46.0"],"error_snippets":["_meta: { \"example.com/canary\": { present: true } },","_meta[\"example.com/canary\"]","This has the same externally visible symptom as #7435/#7476, but IIUC occurs at a different location. The prior fix covered the legacy desktop path, the current ACP path performs two lossy reconstructions.","4. Observe that `structuredContent.present` is available, but `_meta[\"example.com/canary\"]` is absent. `_meta` contains only Goose-derived app routing fields.","A namespaced canary assertion fails independently at each boundary."],"workaround":null,"fixed_in":null,"score":59.0,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#12909","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12909,"title":"Document the Windows installer for goose Desktop","url":"https://github.com/aaif-goose/goose/issues/12909","state":"open","state_reason":null,"labels":[],"created":"2026-10-15T05:39:03Z","updated":"2026-10-22T09:21:50Z","closed":null,"reactions":0,"thumbs_up":0,"comments":4,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"What problem would this solve? PR #12869 (closes #11987) added a signed, per-user NSIS installer (Goose-win32-x64-setup.exe) for goose Desktop on Windows. From the next release it will be published alongside the existing ZIP, but the…","versions":[],"error_snippets":[],"workaround":null,"fixed_in":null,"score":58.1,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#13053","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":13053,"title":"[Bug] goose doctor panics in sqlx-sqlite row.rs after upgrading 1.54.0 -> 1.55.0 (regression of #8719)","url":"https://github.com/aaif-goose/goose/issues/13053","state":"open","state_reason":null,"labels":[],"created":"2026-10-21T16:29:27Z","updated":"2026-10-23T12:42:08Z","closed":null,"reactions":0,"thumbs_up":0,"comments":1,"severity":"high","severity_reasons":["title:breakage"],"topic":"install/update","classes":["install/update","crash/hang","always-on/daemon"],"cosmetic_ui":false,"summary":"Describe the bug After upgrading from 1.54.0 to 1.55.0, goose doctor panics immediately in a background sqlx worker thread: Exit code: 1. This looks like a regression of #8719 (fix: avoid sqlite session creation panic on legacy dbs, closed…","versions":["1.54.0","1.55.0","0.9.0","0.8.6"],"error_snippets":["thread 'sqlx-sqlite-worker-0' (35808) panicked at","note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace","error: Could not create session: no rows returned by a query that expected to return at least one row","fix: avoid sqlite session creation panic on legacy dbs","no rows returned by a query that expected to return at least one row"],"workaround":{"text":"Roll back to 1.54.0, which works against the same database:","source":"issue body","url":"https://github.com/aaif-goose/goose/issues/13053"},"fixed_in":null,"score":58.0,"first_seen":"2026-10-22T09:27:06Z"},{"id":"aaif-goose/goose#13002","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":13002,"title":"GDK: exhausted empty-response retries restart indefinitely","url":"https://github.com/aaif-goose/goose/issues/13002","state":"open","state_reason":null,"labels":[],"created":"2026-10-19T12:27:18Z","updated":"2026-10-20T11:57:03Z","closed":null,"reactions":0,"thumbs_up":0,"comments":2,"severity":"low","severity_reasons":["low engagement"],"topic":"auth/session","classes":["auth/session"],"cosmetic_ui":false,"summary":"Describe the bug A GDK state machine using InferenceRunner can keep calling the provider indefinitely when the provider returns empty responses. The runner makes an initial attempt and three retries, then stores a hidden fallback message…","versions":[],"error_snippets":["operation::{Emitter, MachineEffect, RunStatus},","errors::ProviderError,","enum Effect {","impl From<Message> for Effect {","impl MachineEffect for Effect {"],"workaround":null,"fixed_in":null,"score":47.1,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#12978","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12978,"title":"Support OAuth 2.0 / OIDC JWT authentication across model providers (LiteLLM, OpenAI, Anthropic, etc.)","url":"https://github.com/aaif-goose/goose/issues/12978","state":"open","state_reason":null,"labels":[],"created":"2026-10-17T19:08:38Z","updated":"2026-10-21T19:32:57Z","closed":null,"reactions":0,"thumbs_up":0,"comments":1,"severity":"medium","severity_reasons":["class:auth/session"],"topic":"auth/session","classes":["auth/session","always-on/daemon","self-host/headless"],"cosmetic_ui":false,"summary":"What problem would this solve? In many enterprise and team environments, access to LLM providers—whether through unified gateways like LiteLLM Proxy, corporate API gateways (Kong, Envoy, Apigee), or direct enterprise endpoints for OpenAI…","versions":["2.0"],"error_snippets":["401 Unauthorized","to opt into or configure this shared auth provider alongside existing static API key and","3. **Direct JWT / External Token Source Compatibility**:"],"workaround":null,"fixed_in":null,"score":47.0,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#11582","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":11582,"title":"OAuth authorization URL is incorrect when using Keycloak with pre-registered OAuth client","url":"https://github.com/aaif-goose/goose/issues/11582","state":"open","state_reason":null,"labels":[],"created":"2026-08-26T08:36:32Z","updated":"2026-10-14T19:58:26Z","closed":null,"reactions":0,"thumbs_up":0,"comments":6,"severity":"medium","severity_reasons":["class:auth/session"],"topic":"auth/session","classes":["auth/session","self-host/headless","mcp/tools"],"cosmetic_ui":false,"summary":"Describe the bug I'm testing the pre-registered OAuth client support for streamablehttp extensions introduced in Goose v1.47.0. PR #11182: https://github.com/aaif-goose/goose/pull/11182 Commit: ea6dbf30b8e53ac5a623320eab1b77f61b604166 My…","versions":["1.47.0"],"error_snippets":["enabled: true","I'm testing the pre-registered OAuth client support for `streamable_http` extensions introduced in Goose v1.47.0.","The Goose extension is configured as:","However, `/authorize` is not the Keycloak authorization endpoint in this setup.","The actual Keycloak authorization endpoint is:"],"workaround":null,"fixed_in":null,"score":46.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#13003","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":13003,"title":"Image paths like `C:\\Users\\me\\shot.png` are no longer attached on Windows (regression since v1.39.0)","url":"https://github.com/aaif-goose/goose/issues/13003","state":"open","state_reason":null,"labels":[],"created":"2026-10-19T13:32:57Z","updated":"2026-10-19T14:57:08Z","closed":null,"reactions":0,"thumbs_up":0,"comments":1,"severity":"high","severity_reasons":["title:breakage"],"topic":"install/update","classes":["install/update","self-host/headless","network"],"cosmetic_ui":false,"summary":"Describe the bug Since v1.39.0, goose no longer attaches an image when a message references it by a Windows path such as C:\\Users\\me\\Pictures\\shot.png (or C:/Users/me/Pictures/shot.png). The request sent to the provider only contains the…","versions":["1.39.0","1.38.0","1.55.0"],"error_snippets":[", so a drive-letter path is never considered. Before, each whitespace-separated word was checked with","2. Configure the LiteLLM provider with a vision-capable model (for example `gpt-6-luna`).","3. Run without extensions, so the model cannot open the file with a tool:","4. The image is not attached: the request sent to the provider only contains the text, so the model cannot see the image."],"workaround":null,"fixed_in":null,"score":45.0,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#12817","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12817,"title":"Invalid cron updates remove the existing schedule timer, and an identical retry reports success","url":"https://github.com/aaif-goose/goose/issues/12817","state":"open","state_reason":null,"labels":[],"created":"2026-10-10T19:46:02Z","updated":"2026-10-15T18:46:22Z","closed":null,"reactions":0,"thumbs_up":0,"comments":2,"severity":"medium","severity_reasons":["class:always-on/daemon","class:install/update"],"topic":"always-on/daemon","classes":["always-on/daemon","install/update"],"cosmetic_ui":false,"summary":"Updating an existing schedule with an invalid cron expression disables its timer even though the update returns an error. The schedule remains in the in-memory job list, but its previous cron expression has already been replaced and its…","versions":[],"error_snippets":["with a valid recipe and cron expression","SchedulerError::CronParseError","This matters for unattended automations: a client can receive what looks like a normal validation error, leave the existing automation alone, and assume it will continue running at its previous cadence. Instead, that aut","The affected operation is `Scheduler::update_schedule` in the scheduler-enabled backend. The ACP handler for `_goose/unstable/schedules/update` delegates to this operation and maps a cron parsing error to an invalid-para","Use a scheduler-enabled backend and an existing, non-running schedule. The recipe contents and model configuration are not relevant to this update operation."],"workaround":null,"fixed_in":null,"score":44.4,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#12970","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12970,"title":"Support OAuth 2.0 / OIDC JWT authentication in LiteLLM provider","url":"https://github.com/aaif-goose/goose/issues/12970","state":"open","state_reason":null,"labels":[],"created":"2026-10-17T03:24:33Z","updated":"2026-10-17T03:59:59Z","closed":null,"reactions":1,"thumbs_up":1,"comments":0,"severity":"medium","severity_reasons":["class:auth/session"],"topic":"auth/session","classes":["auth/session"],"cosmetic_ui":false,"summary":"What problem would this solve? Enterprise deployments of LiteLLM proxy often enforce OAuth 2.0 / OIDC JWT authentication (enablejwtauth: true) backed by an identity provider (Keycloak, Okta, Entra ID / Azure AD, Auth0, Dex) rather than…","versions":["2.0"],"error_snippets":["permissions, refreshes expired tokens via"],"workaround":null,"fixed_in":null,"score":44.4,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#12266","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12266,"title":"ACP: MCP extension startup failures never reach the ACP client — session/new succeeds, no session/update, warning only in goose's log file","url":"https://github.com/aaif-goose/goose/issues/12266","state":"open","state_reason":null,"labels":[],"created":"2026-09-20T23:30:20Z","updated":"2026-10-24T04:45:23Z","closed":null,"reactions":0,"thumbs_up":0,"comments":2,"severity":"medium","severity_reasons":["class:install/update","class:mcp/tools"],"topic":"install/update","classes":["install/update","mcp/tools","self-host/headless","network"],"cosmetic_ui":false,"summary":"When an MCP server passed in ACP session/new fails to start, the ACP client is never told. The session/new response is a normal success, no session/update is sent, and nothing appears on stdout or stderr. The host has no way to learn that…","versions":["1.51.0","0.17.0","2.0"],"error_snippets":["WARN goose::agents::agent | Failed to load extension broken-mcp: failed to initialize MCP client:","Send message error Transport [rmcp::transport::worker::WorkerTransport<…streamable…>] … ConnectionRefused","threading.Thread(target=lambda: [errs.append(l.rstrip()) for l in p.stderr], daemon=True).start()","print(\"error in session/new?\", \"error\" in r)","print(\"stderr lines:\", len(errs))"],"workaround":null,"fixed_in":null,"score":42.9,"first_seen":"2026-10-24T08:54:58Z"},{"id":"aaif-goose/goose#13122","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":13122,"title":"Add The Agent Forge to the extensions directory (remote MCP, no auth)","url":"https://github.com/aaif-goose/goose/issues/13122","state":"closed","state_reason":"completed","labels":[],"created":"2026-10-24T11:15:06Z","updated":"2026-10-25T23:59:07Z","closed":"2026-10-25T23:59:07Z","reactions":0,"thumbs_up":0,"comments":1,"severity":"medium","severity_reasons":["class:self-host/headless","class:auth/session"],"topic":"self-host/headless","classes":["self-host/headless","auth/session","mcp/tools","install/update"],"cosmetic_ui":false,"summary":"What problem would this solve? Goose users can't easily see how AI agents behave on everyday business jobs with planted traps, test their own agent against those traps, or check a skill, MCP server or package before trusting it. The Agent…","versions":[],"error_snippets":["Goose users can't easily see how AI agents behave on everyday business jobs with planted traps, test their own agent against those traps, or check a skill, MCP server or package before trusting it. The Agent Forge is a f","The Agent Forge appears in the extensions directory, so a Goose user can add it in one step.","Verification: the JSON stays valid, the docs site builds, and the extension connects in Goose Desktop and lists its tools. Docs: https://theagentforge.io/connect"],"workaround":null,"fixed_in":null,"score":41.6,"first_seen":"2026-10-25T09:11:37Z"},{"id":"aaif-goose/goose#12881","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12881,"title":"Expose goose context token so user can select it manually if auto set tokens size limit is invalid","url":"https://github.com/aaif-goose/goose/issues/12881","state":"open","state_reason":null,"labels":[],"created":"2026-10-13T21:02:24Z","updated":"2026-10-18T16:58:18Z","closed":null,"reactions":0,"thumbs_up":0,"comments":2,"severity":"medium","severity_reasons":["class:auth/session"],"topic":"auth/session","classes":["auth/session"],"cosmetic_ui":false,"summary":"What problem would this solve? This will prevent context of the model from being set incorrectly and allow user to correct the model context size. What would a good outcome look like? when clicking on the model context token, user can…","versions":[],"error_snippets":[],"workaround":null,"fixed_in":null,"score":41.4,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#12016","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12016,"title":"MCP OAuth re-authorizes on every new session after transient refresh failures or refresh rotation races","url":"https://github.com/aaif-goose/goose/issues/12016","state":"open","state_reason":null,"labels":[],"created":"2026-09-11T16:46:57Z","updated":"2026-09-24T15:37:52Z","closed":null,"reactions":1,"thumbs_up":1,"comments":1,"severity":"medium","severity_reasons":["class:auth/session","class:mcp/tools"],"topic":"auth/session","classes":["auth/session","mcp/tools","self-host/headless","network"],"cosmetic_ui":false,"summary":"Describe the bug MCP servers that authenticate via OAuth demand a fresh interactive browser authorization on (nearly) every new goose session, even though valid credentials were previously stored. Once it starts happening, the stored…","versions":[],"error_snippets":["TokenRefreshFailed","per working directory, plus the CLI). With authorization servers that rotate refresh tokens on every use (e.g. Atlassian/Trello, Composio), the process that loses the refresh race receives","token_response: null","[OAuth:...] Token refresh failed ... clearing stored credentials and falling back to browser auth","AuthError::TokenRefreshRejected"],"workaround":null,"fixed_in":null,"score":40.3,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#12084","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12084,"title":"Make extension state and MCP server lifecycle consistent","url":"https://github.com/aaif-goose/goose/issues/12084","state":"open","state_reason":null,"labels":[],"created":"2026-09-15T18:15:24Z","updated":"2026-09-24T05:49:54Z","closed":null,"reactions":0,"thumbs_up":0,"comments":3,"severity":"medium","severity_reasons":["class:self-host/headless","class:mcp/tools"],"topic":"self-host/headless","classes":["self-host/headless","mcp/tools","crash/hang"],"cosmetic_ui":false,"summary":"What problem would this solve? The backend currently treats the extensions selected for a session and the MCP clients running for them as one mutable ExtensionManager. The same component resolves configuration and secrets, starts…","versions":[],"error_snippets":["ExtensionManager","The backend currently treats the extensions selected for a session and the MCP clients running for them as one mutable `ExtensionManager`. The same component resolves configuration and secrets, starts transports, owns li","Extension behavior is consistent across sessions, ACP connections, agent paths, and code mode. A change is visible everywhere the same session is used, session execution context is preserved, capability discovery does no","The backend is easier to evolve without exposing connection and lifecycle details to its callers."],"workaround":null,"fixed_in":null,"score":38.2,"first_seen":"2026-10-25T09:11:37Z"},{"id":"aaif-goose/goose#12337","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12337,"title":"Define origin isolation for MCP App guest content","url":"https://github.com/aaif-goose/goose/issues/12337","state":"open","state_reason":null,"labels":[],"created":"2026-09-21T14:14:25Z","updated":"2026-10-15T16:26:58Z","closed":null,"reactions":0,"thumbs_up":0,"comments":5,"severity":"medium","severity_reasons":["class:mcp/tools"],"topic":"mcp/tools","classes":["mcp/tools"],"cosmetic_ui":false,"summary":"What problem would this solve? MCP App guest content is served from a stable loopback web origin. Without host-enforced origin isolation, separately supplied apps can share browser origin state and may interact with host cookies or storage…","versions":[],"error_snippets":["MCP App guest content is served from a stable loopback web origin. Without host-enforced origin isolation, separately supplied apps can share browser origin state and may interact with host cookies or storage in ways use","Each app's guest content is isolated from local host applications and from other apps while the supported MCP Apps feature set continues to work.","Enforce an opaque-origin sandbox policy without same-origin privileges; serve apps from distinct, unpredictable origins; use separate browser storage partitions or sessions per app; or explicitly define required support "],"workaround":null,"fixed_in":null,"score":37.0,"first_seen":"2026-10-25T09:11:37Z"},{"id":"aaif-goose/goose#11158","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":11158,"title":"[Bug / OAuth]: Goose Desktop v1.45.0: MCP Server that use query parameters fails at connection time in with rmcp \"unexpected server response\" error","url":"https://github.com/aaif-goose/goose/issues/11158","state":"open","state_reason":null,"labels":[],"created":"2026-08-12T03:48:42Z","updated":"2026-10-15T16:26:30Z","closed":null,"reactions":0,"thumbs_up":0,"comments":2,"severity":"medium","severity_reasons":["class:self-host/headless","class:auth/session"],"topic":"self-host/headless","classes":["self-host/headless","auth/session","mcp/tools"],"cosmetic_ui":false,"summary":"Describe the bug Cannot connect to the Datadog MCP server via Oauth Expected behavior When connecting to the Datadog MCP server ( https://mcp.datadoghq.com/api/unstable/mcp-server/mcp?toolsets=core with a custom query string parameter to…","versions":["1.45.0","1.44.0"],"error_snippets":["failed to initialize MCP client: Send message error Transport [rmcp::transport::worker::WorkerTransport<rmcp::transport::streamable_http_client::StreamableHttpClientWorker<reqwest::async_impl::client::Client>>] error: un","Cannot connect to the Datadog MCP server via Oauth","Error message when clicking copy","failed to initialize MCP client: Send message error Transport [rmcp::transport::worker::WorkerTransport >] error: unexpected server response: HTTP 401 Unauthorized: {\"errors\":[\"Unauthorized\"]}, when send initialize reque"],"workaround":{"text":"Downgrading to `1.44.0` restores connectivity. https://github.com/aaif-goose/goose/releases#release-v1.44.0","source":"issue body","url":"https://github.com/aaif-goose/goose/issues/11158"},"fixed_in":null,"score":35.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#12451","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12451,"title":"Define private-network access policy for MCP Apps","url":"https://github.com/aaif-goose/goose/issues/12451","state":"open","state_reason":null,"labels":[],"created":"2026-09-22T21:53:50Z","updated":"2026-10-16T11:54:28Z","closed":null,"reactions":0,"thumbs_up":0,"comments":3,"severity":"medium","severity_reasons":["class:mcp/tools"],"topic":"mcp/tools","classes":["mcp/tools","always-on/daemon","network"],"cosmetic_ui":false,"summary":"What problem would this solve? MCP Apps can declare CSP destinations for network connections, resources, frames, and base URIs. Goose currently accepts loopback IPs, localhost, and other IP literals in those declarations while serving app…","versions":[],"error_snippets":["MCP Apps can declare CSP destinations for network connections, resources, frames, and base URIs. Goose currently accepts loopback IPs, `localhost`, and other IP literals in those declarations while serving app content fr","The supported boundary is documented and enforced consistently across connection, resource, frame, and base-URI declarations. Remote or untrusted apps cannot gain surprising access to local services, while legitimate loc","Verification should cover IPv4 and IPv6 loopback, link-local and metadata ranges, private ranges, DNS resolution/rebinding, redirects where relevant, every supported CSP directive, and the approved local-development exce","Localhost preview is an existing MCP Apps use case, so compatibility and migration behavior need an explicit decision before implementation. #11501 contains related destination-policy precedent for a different MCP transp"],"workaround":null,"fixed_in":null,"score":32.9,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#11021","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":11021,"title":"OAuth credentials for streamable HTTP extensions erased by concurrent session starts — endless re-auth loop","url":"https://github.com/aaif-goose/goose/issues/11021","state":"open","state_reason":null,"labels":[],"created":"2026-08-06T19:30:05Z","updated":"2026-09-29T22:22:48Z","closed":null,"reactions":0,"thumbs_up":0,"comments":3,"severity":"critical","severity_reasons":["title:data-loss/security"],"topic":"auth/session","classes":["auth/session","always-on/daemon","mcp/tools"],"cosmetic_ui":false,"summary":"Stored OAuth credentials for a streamable HTTP extension can be erased by Goose itself when multiple sessions start concurrently, producing an endless re-authentication loop: the user completes the vendor's browser auth, and within…","versions":[],"error_snippets":["in sessions.db, created within 54s of each other). All three eagerly connect enabled extensions, including","clear_credentials_on_post_refresh_auth_failure","Stored OAuth credentials for a streamable HTTP extension can be **erased by Goose itself** when multiple sessions start concurrently, producing an endless re-authentication loop: the user completes the vendor's browser a","Timeline from a single machine, **one goosed process running the entire time** (verified via `ps`):","1. `11:40` — user completes Miro browser auth. Keychain secrets blob (service `goose`, account `secrets`) contains a valid `oauth_creds_miro` entry (client_id + token_response). Verified by reading the blob."],"workaround":null,"fixed_in":null,"score":32.9,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#12849","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12849,"title":"desktop: crash on startup when no theme setting is saved (\"Cannot read properties of undefined (reading 'variant'\")","url":"https://github.com/aaif-goose/goose/issues/12849","state":"open","state_reason":null,"labels":[],"created":"2026-10-12T09:21:16Z","updated":"2026-10-13T21:18:35Z","closed":null,"reactions":0,"thumbs_up":0,"comments":1,"severity":"high","severity_reasons":["title:breakage"],"topic":"crash/hang","classes":["crash/hang"],"cosmetic_ui":false,"summary":"Describe the bug The Goose desktop app shows a \"Honk! An error occurred\" screen with the message: This crashes on startup for users who have never saved a theme preference (i.e., getSetting('theme') returns undefined). The undefined value…","versions":["1.53.0"],"error_snippets":["Cannot read properties of undefined (reading 'variant')","themes[undefined]","The Goose desktop app shows a \"Honk! An error occurred\" screen with the message:","This crashes on startup for users who have never saved a theme preference (i.e., `getSetting('theme')` returns `undefined`). The `undefined` value propagates to `themes[resolvedThemeId].variant` in `ThemeContext.tsx`, wh","3. The app renders the error screen instead of loading."],"workaround":null,"fixed_in":null,"score":32.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#13067","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":13067,"title":"FYI: 1 public goose tool-call failure case packaged as a free regression test","url":"https://github.com/aaif-goose/goose/issues/13067","state":"open","state_reason":null,"labels":[],"created":"2026-10-21T23:26:23Z","updated":"2026-10-21T23:26:23Z","closed":null,"reactions":0,"thumbs_up":0,"comments":0,"severity":"high","severity_reasons":["title:breakage"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"I put together a small open dataset of real coding-agent tool-call failures, built from public GitHub issues: https://github.com/faddacake/agent-failure-evals (v0.1). 1 of the 25 cases comes from an issue in this repo. I'm sharing it in…","versions":["4.0"],"error_snippets":["I put together a small open dataset of real coding-agent tool-call failures, built from public GitHub issues: https://github.com/faddacake/agent-failure-evals (v0.1). 1 of the 25 cases comes from an issue in this repo. I"],"workaround":null,"fixed_in":null,"score":32.0,"first_seen":"2026-10-22T09:27:06Z"},{"id":"aaif-goose/goose#12854","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12854,"title":"load(taskId) returns \"Task not found\" for completed async delegate subagents in Desktop/server sessions (works in standalone CLI)","url":"https://github.com/aaif-goose/goose/issues/12854","state":"closed","state_reason":"completed","labels":[],"created":"2026-10-12T13:14:42Z","updated":"2026-10-15T23:48:45Z","closed":"2026-10-15T23:48:45Z","reactions":1,"thumbs_up":1,"comments":2,"severity":"medium","severity_reasons":["class:self-host/headless"],"topic":"self-host/headless","classes":["self-host/headless","always-on/daemon"],"cosmetic_ui":false,"summary":"Describe the bug In agent sessions running under the goose Desktop app (server-managed backend), results of subagents launched via the delegate tool with async: true cannot be retrieved with load(source: \" \"). The call returns Error: Task…","versions":[],"error_snippets":["You are reproducing a bug for a GitHub issue report. Use ONLY English in everything you write and in every tool call you make. Follow these steps exactly and do nothing else:","1) Call the \"delegate\" tool with: async=true, max_turns=2, and instructions exactly: \"Reply with exactly one line: ENGLISH-REPRO-MARKER-42\"","2) When the subagent completion notification arrives, immediately call the \"load\" tool with source set to that subagent's task ID. Record the exact error message you receive.","3) Call the \"load\" tool with no arguments at all. Record its exact output.","4) Finish with a short English summary listing: the subagent task ID, the exact error from step 2, and the exact output from step 3."],"workaround":null,"fixed_in":null,"score":31.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#11985","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":11985,"title":"MCP server worked with 1.49 and don't work with 1.50","url":"https://github.com/aaif-goose/goose/issues/11985","state":"closed","state_reason":"completed","labels":[],"created":"2026-09-10T10:44:52Z","updated":"2026-09-21T15:31:55Z","closed":"2026-09-21T15:31:55Z","reactions":1,"thumbs_up":1,"comments":4,"severity":"medium","severity_reasons":["class:self-host/headless","class:mcp/tools"],"topic":"self-host/headless","classes":["self-host/headless","mcp/tools"],"cosmetic_ui":false,"summary":"Describe the bug 💡 Before filing, please check common issues: https://goose-docs.ai/docs/troubleshooting 📦 To help us debug faster, attach your diagnostics zip if possible. 👉 How to capture it…","versions":["1.49","1.50","1.0","1.1"],"error_snippets":["failed to initialize MCP client: uncorrelated error response: expected id 0, error response carried server-error","INFO: 10.0.0.207:54932 - \"POST /macrotracker/mcp HTTP/1.1\" 400 Bad Request","Goose shows me an error:","My MCP server shows an error:","It worked with 1.49 and I expect that it will works with 1.50 also."],"workaround":null,"fixed_in":null,"score":30.6,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#12996","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12996,"title":"Subagent can never terminate under Code Mode: recipe__final_output is neither a tool nor an execute_typescript callback (regression in 1.54.0)","url":"https://github.com/aaif-goose/goose/issues/12996","state":"closed","state_reason":"completed","labels":[],"created":"2026-10-19T06:14:35Z","updated":"2026-10-23T01:52:16Z","closed":"2026-10-23T01:52:16Z","reactions":0,"thumbs_up":0,"comments":1,"severity":"high","severity_reasons":["title:breakage"],"topic":"install/update","classes":["install/update","crash/hang","mcp/tools"],"cosmetic_ui":false,"summary":"Since 1.54.0, a subagent spawned while Code Mode (codeexecution) is enabled can never terminate. Its system prompt advertises recipefinaloutput and instructs it that calling that tool is mandatory, but under Code Mode the tool is…","versions":["1.54.0","1.55.0"],"error_snippets":["CALL execute_typescript → ReferenceError: Recipe is not defined","CALL execute_typescript → {\"delivered\":null,\"tried\":[\"Recipe__finalOutput -> …\"]} # 13 name variants","SAY \"I have exhausted every available path to that tool.\"","ERROR Action with id \"recipe/final_output\" does not exist","ERROR Action with id \"final_output\" does not exist"],"workaround":null,"fixed_in":null,"score":30.0,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#13004","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":13004,"title":"Stop and tool timeouts no longer cancel stdio MCP tool calls on 2026-07-28 servers (regression since v1.48.0)","url":"https://github.com/aaif-goose/goose/issues/13004","state":"open","state_reason":null,"labels":[],"created":"2026-10-19T16:44:52Z","updated":"2026-10-21T19:38:07Z","closed":null,"reactions":0,"thumbs_up":0,"comments":0,"severity":"high","severity_reasons":["title:breakage"],"topic":"self-host/headless","classes":["self-host/headless","install/update","mcp/tools","network"],"cosmetic_ui":false,"summary":"Describe the bug Since v1.48.0, goose doesn't send notifications/cancelled when a tool call to a stdio MCP server on protocol 2026-07-28 is stopped (Stop in the desktop, or ACP session/cancel) or hits the extension timeout. goose reports…","versions":["1.48.0","3.4","1.55.0","1.47.0"],"error_snippets":["v1.55.0, 5 s extension timeout","goose: -32603: request timeout after PT5S","edition = \"2021\"","use rmcp::{ErrorData, RoleServer, ServerHandler, ServiceExt};","let line = format!(\"[probe {:>5.1}s] {msg}\\n\", self.started.elapsed().as_secs_f64());"],"workaround":null,"fixed_in":null,"score":30.0,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#12502","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12502,"title":"Possible v1.52.0 regression: Goose Desktop loses chat history after restart","url":"https://github.com/aaif-goose/goose/issues/12502","state":"open","state_reason":null,"labels":[],"created":"2026-09-25T01:48:04Z","updated":"2026-10-02T15:00:50Z","closed":null,"reactions":0,"thumbs_up":0,"comments":3,"severity":"high","severity_reasons":["title:breakage"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"A long-running Goose Desktop conversation disappeared from Goose history after upgrading from v1.51.0 to v1.52.0 and subsequently restarting the application. The recurring user-visible behavior was first observed after the v1.51.0 →…","versions":["1.52.0","1.51.0"],"error_snippets":["The conversation is not merely absent from the sidebar. Its canonical session/title record was not found in the active SQLite database or in the preserved database, WAL, SHM, repair, backup, and renderer-state copies exa","The initial loss event was not captured live, so the exact deletion or persistence failure has not been proven.","The following sequence describes the observed failure pattern:","3. Continue using the conversation over an extended period.","8. Search for the previously existing long-running conversation."],"workaround":null,"fixed_in":null,"score":28.6,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#8638","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":8638,"title":"Goose 1.31.0 panics on startup with existing sessions.db from 1.30.0 (migration v10 orphans sessions)","url":"https://github.com/aaif-goose/goose/issues/8638","state":"closed","state_reason":"completed","labels":[],"created":"2026-04-18T06:46:15Z","updated":"2026-10-16T21:44:01Z","closed":"2026-05-15T16:58:23Z","reactions":1,"thumbs_up":1,"comments":3,"severity":"medium","severity_reasons":["class:install/update","class:crash/hang"],"topic":"install/update","classes":["install/update","crash/hang"],"cosmetic_ui":false,"summary":"After upgrading from Goose 1.30.0 to 1.31.0, starting goose session panics with: The Goose session never starts — the process exits with an error. Schema migration v10 (applied on first run of 1.31.0) introduces a new threads table and…","versions":["1.31.0","1.30.0","0.8.6"],"error_snippets":["thread 'sqlx-sqlite-worker-0' panicked at sqlx-sqlite-0.8.6/src/row.rs:43:46:","Error: no rows returned by a query that expected to return at least one row","sqlite> SELECT COUNT(*) FROM sessions WHERE thread_id IS NULL;","52 -- all existing sessions orphaned","thread_id IS NULL"],"workaround":null,"fixed_in":null,"score":27.9,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#11965","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":11965,"title":"1.50.0 regression: streamable_http MCP extensions fail with \"empty sse stream\" against servers that don't push notifications on the GET channel","url":"https://github.com/aaif-goose/goose/issues/11965","state":"closed","state_reason":"completed","labels":[],"created":"2026-09-09T19:41:32Z","updated":"2026-09-14T20:43:33Z","closed":"2026-09-14T20:43:33Z","reactions":1,"thumbs_up":1,"comments":1,"severity":"high","severity_reasons":["title:breakage"],"topic":"self-host/headless","classes":["self-host/headless","install/update","mcp/tools","network","auth/session"],"cosmetic_ui":false,"summary":"After upgrading from 1.49.0 to 1.50.0, all streamablehttp MCP extensions that worked fine on 1.49.0 fail to connect on 1.50.0, with: and in the CLI log: Bisected to #11827 (\"prefer latest MCP version\"), which changed…","versions":["1.50.0","1.49.0","1.100.0","3.2"],"error_snippets":["Failed to load extension <name>: failed to initialize MCP client: connection closed: discover response","worker quit with fatal: unexpected server response: empty sse stream, when process initialize response","request to establish the server-push SSE channel (per the Streamable HTTP transport). Our server's GET handler (","unexpected server response: empty sse stream","uncorrelated error response"],"workaround":null,"fixed_in":null,"score":27.4,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#12165","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12165,"title":"Define server identity requirements for externally managed local backends","url":"https://github.com/aaif-goose/goose/issues/12165","state":"open","state_reason":"reopened","labels":[],"created":"2026-09-16T23:24:14Z","updated":"2026-09-24T05:50:40Z","closed":null,"reactions":0,"thumbs_up":0,"comments":2,"severity":"medium","severity_reasons":["class:self-host/headless"],"topic":"self-host/headless","classes":["self-host/headless","always-on/daemon","crash/hang","auth/session"],"cosmetic_ui":false,"summary":"What problem would this solve? Desktop supports externally managed backends through settings and environment configuration, including local development services. Users and backend authors need a clear contract for how the client…","versions":[],"error_snippets":["Desktop supports externally managed backends through settings and environment configuration, including local development services. Users and backend authors need a clear contract for how the client establishes server ide","Decide whether external local services must provide authenticated server identity before receiving the shared secret, or whether an explicitly acknowledged trusted-host development mode remains supported. Define the defa","Consider verified or pinned TLS, another supported server-identity mechanism, and the compatibility implications of an explicit development exception. Apply the decision consistently to startup probes and the subsequent ","This is a transport compatibility/design decision, not a request to implement one approach yet. Acceptance criteria should cover existing local development setups, authenticated external services, and clear failures befo"],"workaround":null,"fixed_in":null,"score":26.8,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#9549","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":9549,"title":"Allow agents to register MCP extensions dynamically at runtime","url":"https://github.com/aaif-goose/goose/issues/9549","state":"open","state_reason":null,"labels":[],"created":"2026-06-01T06:52:46Z","updated":"2026-09-16T19:50:47Z","closed":null,"reactions":0,"thumbs_up":0,"comments":2,"severity":"medium","severity_reasons":["class:mcp/tools"],"topic":"mcp/tools","classes":["mcp/tools","always-on/daemon","self-host/headless","auth/session"],"cosmetic_ui":false,"summary":"Please explain the motivation behind the feature request. Identity/credential brokers (e.g. Warden, and similar projects) sit between agents and external services. At session start, the agent calls the broker's discovery endpoint and gets…","versions":[],"error_snippets":["pub enum ManageExtensionAction {","name: String, // identifier for subsequent Enable/Disable","transport: ExtensionTransport, // StreamableHttp | Stdio | Sse","https://broker.example.com/v1/<ns>/mcp_slack/role/slack-publisher/gateway/",", the extension lives in the session's in-memory extension set (not persisted to config) and is targetable by"],"workaround":null,"fixed_in":null,"score":26.8,"first_seen":"2026-10-26T10:12:02Z"},{"id":"aaif-goose/goose#12493","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12493,"title":"UI freezes and \"Install & Restart\" button is unresponsive when updating goose Desktop app on Windows 11","url":"https://github.com/aaif-goose/goose/issues/12493","state":"closed","state_reason":"completed","labels":[],"created":"2026-09-24T18:11:35Z","updated":"2026-10-20T00:04:37Z","closed":"2026-10-20T00:04:37Z","reactions":0,"thumbs_up":0,"comments":4,"severity":"high","severity_reasons":["title:breakage"],"topic":"install/update","classes":["install/update","crash/hang"],"cosmetic_ui":false,"summary":"Description: When attempting to update the goose Desktop application on Windows 11 via the in-app settings (Settings > App > Updates), clicking the Download button works successfully. However, when clicking the subsequent Install & Restart…","versions":[],"error_snippets":["The application completely freezes upon clicking the Install & Restart button. The UI becomes entirely unresponsive, no background installer process is launched, and the app must be forcefully closed via Task Manager or "],"workaround":null,"fixed_in":null,"score":26.2,"first_seen":"2026-10-19T18:38:33Z"},{"id":"aaif-goose/goose#12746","harness":"goose","harness_name":"Goose","repo":"aaif-goose/goose","number":12746,"title":"PreToolUse plugin hooks load but never execute in headless  (main agent)","url":"https://github.com/aaif-goose/goose/issues/12746","state":"closed","state_reason":"completed","labels":[],"created":"2026-10-07T06:12:50Z","updated":"2026-10-21T21:56:08Z","closed":"2026-10-21T21:56:08Z","reactions":0,"thumbs_up":0,"comments":1,"severity":"medium","severity_reasons":["class:self-host/headless","class:mcp/tools"],"topic":"self-host/headless","classes":["self-host/headless","mcp/tools","install/update","crash/hang","auth/session","network"],"cosmetic_ui":false,"summary":"A plugin PreToolUse hook is discovered and loaded (\"Loaded plugin hooks\" appears in the CLI log), but never executes for any tool call made by the main agent in a headless goose run session. The tool runs as if no hook existed. This makes…","versions":["1.50.1"],"error_snippets":["echo \"hook fired\" >> /tmp/hookrepro-fired.log","echo \"denied by policy\" >&2","goose run --text \"Use the Write tool to create leak.txt containing 'leaked'. If denied, quote the denial.\"","{\"level\":\"INFO\",\"fields\":{\"message\":\"Loaded plugin hooks\",\"rule_count\":1,\"events\":\"[\\\"PreToolUse\\\"]\"},\"target\":\"goose::hooks\"}","hook is discovered and loaded (\"Loaded plugin hooks\" appears in the CLI log), but never executes for any tool call made by the **main agent** in a headless"],"workaround":null,"fixed_in":null,"score":24.2,"first_seen":"2026-10-26T10:12:02Z"}]}