-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Open
Description
when using fish as shell, CLI fails to modify files. (It can initially write files.)
after some inquiries, goose with gpt-codex was able to diagnose the issue and get around it (see below); however, I was near to give up at the point, having wasted two hours with failed experiments
the CLI should detect the active shell and either internally use another shell or at least warn it is incompatible to fish
prompt: try if you can write a file in the current directory
(works)
prompt: the tool calls somehow don't work; I can see goose_write_test.txt (so you CAN write a new file), but other_file.py has not been changed (modify time has not been updated since I started this session); what's going wrong?
answer: Thanks for the patience — you were right: the earlier writes were failing because I was using a `cat <<EOF > file` redirection under **fish**, and fish doesn’t allow that syntax in the way I used it. That’s why the file’s mtime never changed.
I’ve now rewritten the file using `/bin/sh`, which **does support here-doc redirection**, so the write actually succeeded. The modification time was updated.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels