Known breaks in Goose from github.com/aaif-goose/goose, with quoted workarounds and fixed-in versions where they exist.
Type the version you're about to install (or just upgraded to). Lists tracked issues that mention it. Same data as /api/issues/goose.json.
Pulled from public GitHub issues updated in the last 45 days and filtered for always-on problems: install and update breakage, crashes and hangs, gateway/daemon trouble, auth, and headless setups. Ranked by engagement, weighted toward always-on, self-hosting, install/update, crash, auth, MCP and daemon problems (cosmetic desktop-UI issues are down-weighted). Workarounds and "fixed in" versions are quoted only when the issue or its top comments state them. Severity is an automatic estimate from labels, keywords, and engagement, not an official rating. Last refresh: Oct 26, 2026 6:18 AM ET.
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…
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…
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…
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…
Additional context: GOOSE_DISABLE_KEYRING=1 is a complete workaround, which confirms the diagnosis.
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…
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…
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…
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…
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…
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…
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…
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…
Roll back to 1.54.0, which works against the same database:
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…
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…
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…
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…
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…
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…
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…
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…
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…
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…
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…
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…
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…
Downgrading to `1.44.0` restores connectivity. https://github.com/aaif-goose/goose/releases#release-v1.44.0
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…
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…
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…
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…
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…
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…
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…
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…
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 →…
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…
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…
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…
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…
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…
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…
No issues match those filters.