Goose CLI & Desktop (Windows 11) cannot execute scripts or access filesystem [Autopilot model selector] + box title missing first letter

[freccon]

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

1. Enable Autopilot mode (via config file)
2. Open Goose Desktop or CLI on Windows 11
3. Ask Goose to execute any filesystem task, such as:
   • Run a script
   • Create a zip file
   • Read a file
4. Observe that none of these tasks execute (no output, no files created, nothing read)
5. Switch to Worker/Lead mode (change config.yaml )
6. Re-open a session and re-run the exact same tasks — now they work correctly
7. Look at any tool box title rendered in the UI (Desktop App)
8. Notice the first letter is missing (e.g., Hell instead of Shell)

---

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]

Hi @freccon, by autopoilet mode, do you mean autonoums mode ?

[freccon]

Hi @Abhijay007 , I mean the "Autopilot model selector".

[DOsinga]

looks like @michaelneale worked on autopilot, so maybe he has thoughts?

the missing first letter on windows usually is somehow related to path problems where a \ gets slipped in, but it doesn't look like that is the case here. can you share the diagnostics report?

[freccon]

Hi @DOsinga , I’ve attached the diagnostics files. Hopefully they help clarify what’s happening on my side.

Please let me know if you need any additional logs or tests.

Diagnostics_goose.zip

[michaelneale]

woah that is amusing - "Hell" for shell... amazing...

@freccon unfortunately in the diagnostics i don't see any config with autopilot on - can you can tge config.yml directly when you run it in the "Hell" mode?

@DOsinga yeah I think we should remove this too, it is "X" for experimental in config for that reason, and now I think we have a future way to do this, we can retire it then?

[thiago-scherrer]

I'm having the same problem here. I can no longer interact with files, run local commands, etc.

goose version: 1.14.0 OS: Ubuntu 24.04.3 LTS

[michaelneale]

@thiago-scherrer what models are you using and can you share your config please? @freccon also if you get a chance, as cant reproduce this with info here.

[freccon]

Hi @michaelneale, thanks for the follow-up, and sorry for the delay. I'm sharing my config.yml as requested. This is the exact configuration used when the issue occurs

config_auto.yaml

Something that looks a bit odd to me is that the logs do show Autopilot being picked up and initialized correctly, for example:

It’s possible I missed these files earlier, since I had several sessions open while trying to get Autopilot working.

Let me know if I can help with something else.

[michaelneale]

thanks @freccon yeah that is really weird, and if you use that exact same model just plain, or with lead worker - it doesn't truncate?

Autopilot was an experimental feature so I wouldn't lean on it too much right now, but I am curious why it would fail in this mode... like it is messing up the context somehow...

[freccon]

That's right, it works perfectly in worker/lead mode. I know Autopilot is experimental 😅, but I wanted to try it to explore different models and “modes.” For now I can keep going with worker/lead mode, everything runs fine there.

At one point I even thought the problem might be related to Gemini-Claude combination, so I switched almost everything to Claude (but the same error persisted)

Still, I’m also curious why Autopilot behaves this way. thx

[thiago-scherrer]

@thiago-scherrer what models are you using and can you share your config please? @freccon also if you get a chance, as cant reproduce this with info here.

my config.yaml

OPENAI_BASE_PATH: v1/chat/completions
GOOSE_PROVIDER: openai
OPENAI_HOST: https://api.openai.com
GOOSE_MODEL: gpt-5
extensions:
  pdf:
    enabled: false
    type: stdio
    name: pdf
    description: ''
    cmd: uvx
    args:
      - mcp-read-pdf
    envs: {}
    env_keys: []
    timeout: 300
    bundled: null
    available_tools: []

  mcpatlassian:
    enabled: true
    type: sse
    name: mcpatlassian
    description: ''
    uri: "<MC_ATLASSIAN_SSE_URI>"
    envs: {}
    env_keys:
      - "xxx"
    timeout: 300
    bundled: null
    available_tools: []

  graph-memory:
    enabled: true
    type: sse
    name: graph-memory
    description: ''
    uri: "<GRAPH_MEMORY_SSE_URI>" 
    envs: {}
    env_keys: []
    timeout: 300
    bundled: null
    available_tools: []

  slack:
    enabled: true
    type: stdio
    name: slack
    description: slack
    cmd: npx
    args:
      - -y
      - slack-mcp-server@latest
    envs: {}
    env_keys:
      - "xxx"
    timeout: 300
    bundled: null
    available_tools: []

  extensionmanager:
    enabled: false
    type: platform
    name: Extension Manager
    description: Enable extension management tools for discovering, enabling, and disabling extensions
    bundled: true
    available_tools: []

  chatrecall:
    enabled: false
    type: platform
    name: chatrecall
    description: Search past conversations and load session summaries for contextual memory
    bundled: true
    available_tools: []

  todo:
    enabled: false
    type: platform
    name: todo
    description: Enable a todo list for Goose so it can keep track of what it is doing
    bundled: true
    available_tools: []
GOOSE_MODE: auto

[fernandaspets]

maybe it has to do with this? -32602: Missing 'file_text' parameter for write command ─── text_editor | developer ────────────────────────── path: ~/projects/goose/test_example.py command: write view_range: 1, 10

-32602: Missing 'file_text' parameter for write command^CThe tool calling loop was interrupted.

[jpschreiter]

Same problem on Mac OS using goose installed via homebrew with version 1.16.1. Appears in Autonomous and Manual mode.