Configure goose to use non-Bash shell syntax

[hongquan]

My primary shell is Fish. But when goose needs to run some shell command, it always write it in Bash syntax and run in Fish, getting syntax errors. Even after hitting so many syntax errors, it still keep writing command in Bash syntax.
Is there a way to configure goose to use Fish syntax?

[DOsinga]

I don't think this works today, but it should be fixeable /cc @baxen -- send us a PR? also this would be good to discuss on Discord

[VectorPeak]

There isn't a config knob today that tells goose “generate fish syntax”. The shell tool is effectively being used with bash/POSIX assumptions, so running it under fish is going to keep producing mismatches.

Best workaround is to start goose with a POSIX shell in SHELL, even if your interactive shell is fish:

env SHELL=/bin/bash goose

or, if you prefer zsh:

env SHELL=/bin/zsh goose

That won’t make goose generate fish syntax, but it should stop bash-style commands from being executed by fish. A proper fix would likely be either making the shell used by the tool configurable, or passing the active shell info into the model/tool prompt so it can generate compatible commands.

[hongquan]

To share with someones running into the same issue, I create a ~/.local/bin/goose file with this content:

#!/bin/sh
SHELL=/usr/bin/bash ~/.local/share/mise/installs/github-aaif-goose-goose/latest/goose "$@"

Make the file executable.

This file is necessary if we run Goose indirectly as ACP server (like via Toad).

The "mise/installs/github-aaif-goose-goose" path is because I installed Goose via mise (to let mise track Goose update for me).

Update:

• SHELL override still does not work if Goose is invoked from Toad (Goose still run Bash command in Fish shell).

[hongquan]

The SHELL override does not work.