Execution failed: Failed to write file: Read-only file system (os error 30)

[Gavriel94]

Using:

• Goose desktop app
• macOS Sequoia 15.2
• michaelneale/deepseek-r1-goose:70b

Prompt:

"Navigate to Life/ImportantDocs and create a new file called shopping_list.csv containing - bread - eggs - milk - cheese"

Output:

• Execution failed: Failed to write file: Read-only file system (os error 30)

---

michaelneale/deepseek-r1-goose:70b was able to find the tool and execute the command successfully with Goose CLI

[salman1993]

Can you please check:

1. if you have write permissions in the directory where Goose is running? (you can see this in the bottom left) you can try creating a file in that directory.

Or you can try opening goose in a new directory

2. The directory you are trying to write to is not a read-only mounted filesystem / NFS that's not configured to write

This is the error you're running into.

[Gavriel94]

I have permissions in the directory where Goose is running, I created it specifically to tests its capabilities. The directory is on my local machine in an offline folder (i.e. not an iCloud folder)

[ahau-square]

Just confirming that this also fails for other models? Deepseek r1 isn't necessarily a great choice since tool calling isn't native for it, though this issue appears unrelated.

I'm not able to reproduce this and I'm also on macOS Sequoia 15.2

[Gavriel94]

The issue is only in the GUI. I have updated to 1.0.3 and it's still happening with both Deepseek models. The 70b version cannot access the tool and the 14b version (:latest) doesn't know what directory it's in and just provides instructions for me to do it myself.

The CLI works flawlessly so the tooling is working, it's as if Deepseek doesn't know its "in goose" when I'm using the GUI.

[salman1993]

@Gavriel94 can you check if your ~/.config has read & write permissions. Goose needs that access to create the config & log directory.

[Gavriel94]

@salman1993 ~/.config has read and write permissions.

~/.config/goose contains:

• config.yaml
• logs/
• mcp-hermit/
• memory/
• sessions/

[zakiali]

@Gavriel94 Just wanted to follow up on this. Are you still running into these issues with the most recent versions?