Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Goose's UI doesn't allow you to change Goose's permissions #1469

Closed
amayers opened this issue Mar 3, 2025 · 1 comment · Fixed by #1434
Closed

Goose's UI doesn't allow you to change Goose's permissions #1469

amayers opened this issue Mar 3, 2025 · 1 comment · Fixed by #1434

Comments

@amayers
Copy link

amayers commented Mar 3, 2025

Describe the bug

I asked Goose to clear your log files. Instead of clearing Goose's log files, it started running a find/delete on my entire computer for *.log files. The documentation, says that you can change Goose's permissions from Auto to Approve Mode or Chat Mode. However there doesn't appear to be any way to do that in the UI. The instructions in that doc don't work.

To Reproduce
Steps to reproduce the behavior:

  1. Install Goose
  2. Search UI for permissions settings
  3. Read doc which says to go to Terminal and run goose configure.
  4. Run goose configure in the terminal. Get a zsh: command not found: goose
  5. Try telling goose to change it's permissions (see screenshot). It is trying to change file permissions, instead of Goose's permissions setting. Either way it fails to do this.

Expected behavior
I would be able to make Goose less destructive, and have to confirm before it just starts deleting all files of given pattern off my system.

Screenshots
Image

Please provide following information:

  • OS & Arch: macOS 15, M3
  • Interface: UI
  • Version: 1.0.9-block.202502252251-e51b7 (1.0.9-block.202502252251-e51b7)
  • Extensions enabled: Default
  • Provider & Model: Default
@yingjiehe-xyz
Copy link
Collaborator

yingjiehe-xyz commented Mar 3, 2025

The mode control should be supported in #1434, will be released soon and would like to hear any feedback on it

@yingjiehe-xyz yingjiehe-xyz linked a pull request Mar 3, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants