With the latest released version of goose i.e https://github.com/block/goose/releases/tag/v1.21.0 , mcp server is not able to connect

[Amankkc]

Describe the bug

With the latest released version of goose i.e https://github.com/block/goose/releases/tag/v1.21.0 , mcp server is not able to connect . It was working fine with previous version i.e https://github.com/block/goose/releases/tag/v1.20.1 . Please help in fixing this or let us know if there is any configuration changes that needs to be done .

💡 Before filing, please check common issues:
https://block.github.io/goose/docs/troubleshooting

📦 To help us debug faster, attach your diagnostics zip if possible.

Error logs
:mag: Test: whoami_test288 Validates that the agent can execute 'whoami' and returns user information289 :package: Setup... :white_check_mark:290 :round_pushpin: Step 1/1: Execute whoami command291 :robot_face: Execute... :x:292 :x: Error: step 1 execution failed: command failed: exit status 1 (output: 293 Help improve goose294295 Would you like to help improve goose by sharing anonymous usage data?296 This helps us understand how goose is used and identify areas for improvement.297298 What we collect:299 • Operating system, version, and architecture300 • goose version and install method301 • Provider and model used302 • Extensions and tool usage counts (names only)303 • Session metrics (duration, interaction count, token usage)304 • Error types (e.g., "rate_limit", "auth" - no details)305306 We never collect your conversations, code, tool arguments, error messages,307 or any personal data. You can change this anytime with 'goose configure'.308309 Error: not connected310

👉 How to capture it: https://block.github.io/goose/docs/troubleshooting/diagnostics-and-reporting/

Expected behavior
A clear and concise description of what you expected to happen.

MCP server should be able to connect as it was working with earlier versions .

---

Screenshots
If applicable, add screenshots to help explain your problem.

---

Please provide the following information

• OS & Arch: [e.g. Ubuntu 22.04 x86] ; MacOS
• Interface: [UI / CLI] Both
• Version: [e.g. v1.0.2] v1.21.0

[DOsinga]

Hi! we actually release 1.21.1 in response to this since we broke something. sorry! can you try that?

[Amankkc]

Hi! we actually release 1.21.1 in response to this since we broke something. sorry! can you try that?

I am not able to see 1.21.1 release here https://github.com/block/goose/releases 🤔

[DOsinga]

oh, you are right. we did break something in 1.20. and fixed this in 1.20.1 but maybe this came back /cc @zanesq

[DOsinga]

can you share a diagnostics report?

[Amankkc]

After checking it locally and the https://github.com/block/goose/ codebase , found that GOOSE_TELEMETRY_ENABLED: false was required to be added in config.yaml file when it requires to run in auto mode for this error :

Help improve goose

Would you like to help improve goose by sharing anonymous usage data?
This helps us understand how goose is used and identify areas for improvement.

What we collect:
  • Operating system, version, and architecture
  • goose version and install method
  • Provider and model used
  • Extensions and tool usage counts (names only)
  • Session metrics (duration, interaction count, token usage)
  • Error types (e.g., "rate_limit", "auth" - no details)

We never collect your conversations, code, tool arguments, error messages,
or any personal data. You can change this anytime with 'goose configure'.

◇  Share anonymous usage data to help improve goose?
│  Yes 
│

In cli mode , its ask for manual intervention to enable/disable telemetry and post human intervention it work fine.

But my concern is why in the previous version auto mode was able to handle this and with the latest version https://github.com/block/goose/releases/tag/v1.21.2 this additional configuration GOOSE_TELEMETRY_ENABLED: false is required in order to avoid human intervention .

Also , the users should be let known about this changes . Hope it is available in some docs or can you please highlight if it is documented any where else for future reference .

[Amankkc]

@DOsinga As of now the issue is resolved, I manually went through the codebase and found that GOOSE_TELEMETRY_ENABLED: false was required to be added in config.yaml file to fix the issue in latest version of goose (auto mode). Please see this comment for more reference -#6659 (comment) .

Can you please help in pointing the document which mention any configuration changes with latest version that requires to be added (As I am not able to find any) . if there is not such documentation yet then it will be great if someone can take care of mentioning/documenting the additional config changes that will be required with latest version releases. it will help the users getting rid of issues and manual debugging . Thanks !!

[DOsinga]

@Amankkc - sorry for the super late reply, missed this. I think this works (now) as expected. in interactive mode the app will ask you whether you want to opt in if that variable is not set and updates the config.yaml. in non interactive mode, it defaults to false. so closing for now, but feel free to reply if you feel otherwise