Feature request: Configure certain extensions to be enabled in chat mode #2562
bendavis78
started this conversation in
Ideas
Replies: 1 comment
-
This sounds like an interesting idea. The one thing that I am trying to understand is how you would make goose do tool calls it does in other modes in chat-only mode. If you have a good solution on what to make configurable in config.yaml already, I'd highly recommend opening a PR with a solve! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
There are times when I'd just like to chat with the model w/o making changes to code, but still want it to have access to extensions. For example, I want it to read documentation from an internal knowledge base, or look at code and github. I can put it into "approve" mode, but it still attempts to suggest changes and that's not ideal. Also sometimes I would just like it to use such tools automatically.
Ideally we would want goose to only call tools that do not make changes to the filesystem or any other state. I don't believe there is a standard way to do this other than to have the LLM guess at which tools are safe to use in chat.
One easy solution to this would be to just make it configurable in
config.yaml
. Just have a boolean option forchat_mode
that we can set toTrue
. This gives the user control over which tools they want to be used in chat.Beta Was this translation helpful? Give feedback.
All reactions