"-32603: No such file or directory (os error 2)" when trying to run commands
Describe the bug
I can chat with models through ollama, but commands output "-32603: No such file or directory (os error 2)". Tested with qwen3:30b, qwen3:14n and gpt-oss:20b.
commands work in the cli version, using ollama and claude code
To Reproduce open goose 1.7.0, use ollama, pick any model, ask model to do any command, for example "do pwd", or "do an ls"
result:
Okay, the user is asking to "do pwd". The pwd command in the shell stands for "print working directory", which shows the current directory path. Since I need to execute this command, I should use the developer__shell tool. Let me check the parameters for that function. The required parameter is "command", so I'll set the command to "pwd". I don't need any other parameters here. Just call the shell function with "pwd" as the command. That should return the current directory path to the user.
running pwd
Tool details command - pwd Output -32603: No such file or directory (os error 2)
Expected behavior I expect parity with the CLI tool, it being able to run the command and return the results.
Screenshots
Please provide following information:
- OS & Arch: macos 15.5 (24F74)
- Interface: [UI]
- Version: [1.7.0]
- Extensions enabled: [Audio visualiser, Computer controller, developer, memory]
- Provider & Model: [tested with Ollama - qwen3:30b, qwen3:14b, gpt-oss:20b and Claude Code - claude-sonnet-4-20250514]
I tested a lot of other basic commands, all return the same error
I am also getting this same behavior running on Arch Linux with Goose installed via the aur/codename-goose-bin source, any luck in getting anything to work? I've tested with Gemini 2.5 Pro and Gemini 2.5 Flash, but both behave the same.
the command line works fine for me. any way we can make this more specific and reproduceable?
Is it possible your system doesn't have bash in the system path? Seems unlikely, but goose tries to use either $SHELL or bash to run its shell commands, and doesn't check first that it is available
Please re-open if something like this keeps occurring in recent versions of goose. They should better handle a missing shell (if that is indeed what was happening here)