block
Restrict access to files or paths
Sorry in advance if this has come up earlier!
When discussing code with Goose, it's very practical to give it access to the OS path where the code project is located. However, this would give Goose access to e.g. .env files nested within the project, which in turn might contain secret keys or passwords. Is there a way to make Goose and all of its extensions unable to access some files or paths? If not, this is an important feature any security minded developer needs. A .gooseignore file (just like .gitignore) could be one way of solving this?
@ZhenLian contribution very welcome!
I think a .gooseignore is a great idea and we could ensure it is skipped in file reads at a minimum
Closing this since it is done, here is a documentation https://block.github.io/goose/docs/guides/using-gooseignore/. Thanks @ZhenLian for your contribution
