# Goose: known issues context pack (KnownFix)
Generated 2026-10-26T10:18:14Z from github.com/aaif-goose/goose. Auto-extracted; verify via links. Source: https://knownfix.ai/issues/goose/
Fields: severity (auto-estimate) | symptom | versions mentioned | workaround (quoted from issue/comments, if any) | fixed-in (if referenced).

## Active
- [MEDIUM] Render A2UI embedded resources from MCP tool results in goose desktop (https://github.com/aaif-goose/goose/issues/12703)
  - symptom: Proposal: goose doesn't support A2UI today
  - error: `capabilities.extensions`
  - workaround: none stated
- [MEDIUM] Support SEP-2640 Skills Extension (skills over MCP) as host (https://github.com/aaif-goose/goose/issues/12068)
  - symptom: What problem would this solve? MCP has no standard way to ship workflow instructions alongside the tools they describe
  - error: `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. `
  - workaround: none stated
- [MEDIUM] Define an OS sandbox boundary for shell and tool subprocesses (https://github.com/aaif-goose/goose/issues/12805)
  - symptom: What problem would this solve? goose can already ask before a tool runs (approve, smartapprove) and can deny a tool entirely
  - versions: 1.25.0
  - error: `tool executes the model-supplied command with no OS boundary. The default`
  - workaround: none stated
- [CRITICAL] OAuth succeeds, then the extension fails, when the token exceeds Windows Credential Manager's 2560-char limit (https://github.com/aaif-goose/goose/issues/12905)
  - symptom: Describe the bug: On Windows, a remote MCP extension fails to load after a successful authorization
  - versions: 1.54, 1.53
  - error: `On Windows, a remote MCP extension fails to load after a successful authorization. The browser shows Goose's own "Authorization Success" page, then the extensio`
  - workaround: Additional context: GOOSE_DISABLE_KEYRING=1 is a complete workaround, which confirms the diagnosis. [issue body]
- [MEDIUM] feat(tasks): unified task registry + tasks platform extension (background processes, timers, wait_for wake-ups) (https://github.com/aaif-goose/goose/issues/11740)
  - symptom: 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
  - error: `), no cancel-with-partial-output, no structured lifecycle — every ad-hoc`
  - workaround: none stated
- [MEDIUM] Support MCP's server.json and mcp.json import (https://github.com/aaif-goose/goose/issues/10839)
  - symptom: goose has its own repository for MCP servers but given that there is an MCP server for everything now, this concept is outdated
  - workaround: none stated
- [MEDIUM] Desktop (Windows, 1.53.0): turn-final assistant messages ([thinking + text], no tool call) missing from chat view, while (https://github.com/aaif-goose/goose/issues/13011)
  - symptom: 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; 
  - versions: 1.53.0, 5.3-flash, 1.51
  - error: `(551 message rows),`
  - workaround: none stated
- [MEDIUM] Add harness-level progressive MCP tool discovery (https://github.com/aaif-goose/goose/issues/13022)
  - symptom: Add harness-level progressive tool discovery so Goose can keep most MCP tool schemas out of the model context until they are relevant
  - error: `A small always-visible discovery tool could search across configured MCP servers using server/tool hints, activate matching tools for the session, and refresh t`
  - workaround: none stated
- [MEDIUM] Goose APP UPDATE BUG (https://github.com/aaif-goose/goose/issues/13128)
  - symptom: 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
  - versions: 1.0.2
  - error: `4. See error`
  - workaround: none stated
- [MEDIUM] ACP desktop drops CallToolResult._meta before MCP App notification (https://github.com/aaif-goose/goose/issues/11323)
  - symptom: 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
  - versions: 1.46.0
  - error: `_meta: { "example.com/canary": { present: true } },`
  - workaround: none stated
- [MEDIUM] Document the Windows installer for goose Desktop (https://github.com/aaif-goose/goose/issues/12909)
  - symptom: 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
  - workaround: none stated
- [HIGH] [Bug] goose doctor panics in sqlx-sqlite row.rs after upgrading 1.54.0 -> 1.55.0 (regression of #8719) (https://github.com/aaif-goose/goose/issues/13053)
  - symptom: 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
  - versions: 1.54.0, 1.55.0, 0.9.0
  - error: `thread 'sqlx-sqlite-worker-0' (35808) panicked at`
  - workaround: Roll back to 1.54.0, which works against the same database: [issue body]