Bug Report: Goose v1.1.3 Not Responding to Prompts After Clean Install

Environment

• Goose Version: 1.1.3 (latest as of July 2025)

• Operating System: Windows 10 / 11 (please confirm exact version)

• Installation Method: Extracted official ZIP file into C:\Goose\Goose-1.1.3\dist-windows

• VPN: Disabled

• Security Software: Malwarebytes (whitelisted https://api.anthropic.com)

• API Keys:

  • Defined via user environment variables
  • Verified using echo %KEY% in CMD

• LLM Providers Tested: Anthropic (multiple keys), OpenAI, OpenRouter

Describe the Bug

After performing a clean installation of Goose Desktop v1.1.3, the application launches correctly, but does not respond to any prompts. Typing and submitting a prompt results in no visible response or network activity. No logs are written and no UI error or status message appears.

Steps to Reproduce

1. Deleted all previous Goose installations and configuration files, including:

   • C:\Goose\Goose-1.1.3\
   • %LocalAppData%\Goose
   • Residual registry/config/cache files

2. Restarted the system

3. Extracted the latest Goose v1.1.3 ZIP to a fresh folder

4. Verified API keys via CMD (echo %ANTHROPIC_API_KEY%, etc.)

5. Disabled VPN and ensured endpoint access

6. Launched Goose.exe and attempted to send a prompt

Expected Behavior

The app should accept the prompt and respond via the selected provider or provide diagnostic feedback/logs if it fails.

Actual Behavior

• Goose launches normally
• Prompts can be typed and submitted
• Nothing happens (no response, no network activity, no log)
• Previously encountered 404 Not Found error; now absent but app still non-functional

Additional Context

• Attempted Goose.exe > goose_output.log 2>&1 — no logs captured
• Verified that settings.json and claude_desktop_config.json do not exist
• Suspect: undocumented config requirement or failed provider handshake
• Version 1.0.37 previously worked before clean wipe

Please advise if this may be linked to missing dependencies, broken provider config, or a known regression in 1.1.3.

Thank you.