-
Notifications
You must be signed in to change notification settings - Fork 2k
Open
Labels
p3Priority 3 - LowPriority 3 - Low
Description
When using Goose v1.14.0 on Windows 11, both the CLI and Desktop app fail to execute scripts, create files, read files, or run any filesystem-related commands when Autopilot mode is enabled ( configured in config.yaml )
This issue does not occur in Worker/Lead mode — the exact same scripts/tasks run normally there.
This confirms the problem is specific to Autopilot.
Additionally, the UI has a rendering bug:
The first letter in the tool box title is always missing.
For example, instead of Shell, it displays Hell.
To Reproduce
- Enable Autopilot mode (via config file)
- Open Goose Desktop or CLI on Windows 11
- Ask Goose to execute any filesystem task, such as:
- Run a script
- Create a zip file
- Read a file
- Observe that none of these tasks execute (no output, no files created, nothing read)
- Switch to Worker/Lead mode (change config.yaml )
- Re-open a session and re-run the exact same tasks — now they work correctly
- Look at any tool box title rendered in the UI (Desktop App)
- Notice the first letter is missing (e.g.,
Hellinstead ofShell)
Expected behavior
- Autopilot mode should execute scripts and shell commands normally on Windows 11
- Creating, reading, and writing files should work consistently across all modes
- UI tool box titles should display their full text without missing the first character
Screenshots
Please provide the following information
- OS & Arch: Windows 11 x86_64
- Interface: CLI & Desktop
- Version: v1.14.0
- Extensions enabled: developer , extension manager, chatrecall, todo
- Provider & Model: Vertex AI – Gemini & Claude (Anthropic)
Additional context
- The issue is isolated to Autopilot model selector — Worker/Lead mode run scripts and filesystem commands correctly
Abhijay007 and thiago-scherrer
Metadata
Metadata
Assignees
Labels
p3Priority 3 - LowPriority 3 - Low