From bc2229889d39da0f4acb22bfe7b4fe3ba18aab20 Mon Sep 17 00:00:00 2001 From: Angie Jones Date: Mon, 17 Feb 2025 11:27:41 -0600 Subject: [PATCH] docs: troubleshooting - last resort tip (#1262) --- documentation/docs/troubleshooting.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/documentation/docs/troubleshooting.md b/documentation/docs/troubleshooting.md index 7c3e997913..52535f9c75 100644 --- a/documentation/docs/troubleshooting.md +++ b/documentation/docs/troubleshooting.md @@ -172,9 +172,9 @@ An example is the GitHub extension whose command is `npx -y @modelcontextprotoco --- -### macOS Permission Issues (M3 Macs) +### macOS Permission Issues -If you encounter an issue where the Goose desktop app shows no window on launch, it may be due to file and folder permissions. This typically happens because Goose needs read and write access to the `~/.config` directory to create its log directory and file. +If you encounter an issue where the Goose Desktop app shows no window on launch, it may be due to file and folder permissions. This typically happens because Goose needs read and write access to the `~/.config` directory to create its log directory and file. #### How to Check and Fix Permissions: @@ -204,6 +204,15 @@ If you encounter an issue where the Goose desktop app shows no window on launch, ```sh ls -ld ~/.config ``` + +If you still experience issues after fixing permissions, try launching Goose with superuser (admin) privileges: +```sh +sudo /Applications/Goose.app/Contents/MacOS/Goose +``` + +:::note +Running Goose with sudo may create files owned by root, which could lead to further permission issues. Use this as a troubleshooting step rather than a permanent fix. +::: --- ### Connection Error with Ollama Provider on WSL