-
Notifications
You must be signed in to change notification settings - Fork 11
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
feat: add global optional user goosehints file #73
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No concerns with the implementation, just some thoughts below:
Developers typically work within a technical domain, and I'm guessing they would use this concept of global goosehints to describe information relevant to that domain that is applicable across projects.
However, sometimes you use Goose to explore other domains (e.g. working in a frontend project despite being an ML engineer), where some of this context would end up disrupting Goose's performance.
A couple ideas:
-
Perhaps it would be worthwhile prompting users on
goose session start
to see if they want to use their global goosehints for that particular session? -
Another option could be having goosehints be added sequentially from parent directories from the CWD. That could mean you would have some root level goosehints, as well as project level goosehints, etc. An example below:
~/Development/.goosehints
~/Development/java/.goosehints
~/Development/java/buyer-subs/.goosehints
@lukealvoeiro yeah I did think of that - when you say sequentially added - you mean when goose starts a session or when code moves around dirs as part of the session? |
could we put this in |
yep could be in goose config - but I don't know if we want to commit to making it more complicated/smart just yet? ease into it? |
is in goose config dir now |
addresses: #72
from
~/.goosehints
: