Stability Issues Affecting Recent Goose Versions

[alexhancock]

We are aware of stability issues affecting different recent versions of goose. I am starting this centralized tracker to document and drive each of them to resolutions.

Goose Stability Issues Tracker

v1.1.4

Issue	Description	Filer	Status	Resolution PR
N/A	Frequent 400s with "Bad Request" when interacting with model providers	alexhancock	Believed resolved	#3660
#3739	Goose will stop performing tool calls even when it seems to be in an active loop that has not completed, and despite it saying it will call further tools	alexhancock	Open	N/A

main + v1.2.0 RC

Issue	Description	Filer	Status	Resolution PR
#3739	Goose will stop performing tool calls even when it seems to be in an active loop that has not completed, and despite it saying it will call further tools	alexhancock	Open	N/A
	Whenever markdown code files are rendered the app becomes unresponsive to clicks/interaction	alexhancock	Open	N/A
	Context token usage tracker frequently displays 0 tokens used after several rounds of tool calling	alexhancock	Open	N/A
	Cannot install fetch extension - Times out after 5 minutes with error: Error activating extension: Failed to add extension configuration, error: Initialization(Stdio { name: "fetch", cmd: "/Users/USERNAME/proj/goose/goose/ui/desktop/src/bin/uvx", args: ["mcp-server-fetch"], envs: Envs { map: {} }, env_keys: [], timeout: Some(300), description: None, bundled: None }, McpServerError { method: "initialize", server: "", source: ServerBoxError(Elapsed(())) })	DOsinga	Open	N/A
	Context token usage tracker frequently displays 0 tokens used after several rounds of tool calling	alexhancock	Open	N/A
	Adding new extension does not reflect in the list of extensions until you do something else	DOsinga	Open	N/A
#3887	Goose sometimes stalls out mysteriously when in the midst of a session	alexhancock	Open	N/A

---

Usage Instructions:

• Issue: Brief title/summary of the stability issue
• Description: Detailed description of the problem, steps to reproduce, etc.
• Related GitHub Issues/PRs: Link to relevant GitHub issues or pull requests (e.g., #123, PR #456)
• Filer: Name or username of the person who reported the issue
• Status: Current status (e.g., Open, In Progress, Fixed, Won't Fix, Duplicate)
• Resolution PR: Link to the pull request that fixes the issue (e.g., PR #789)

[michaelneale]

Still seeing this with main as of 5th Aug and databricks + sonnet4 (but I was also seeing upstream errors, and saw separately api errors direct with anthropic so it is hard to tell if this is the case).

[alexhancock]

The issues captured in this have not been issues in our testing and usage of goose recently. Going to close out the centralized tracker - we can track individual issues still affecting the app.