-
Notifications
You must be signed in to change notification settings - Fork 139
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
Improve CLI getting started experience with Bee by customizing to a use case #148
Labels
enhancement
New feature or request
Comments
mmurad2
changed the title
Improve ability to customize Bee for a given use case
Improve CLI getting started experience with Bee by customizing to a use case
Nov 11, 2024
Scope subject to change depending on current discussion. Feel free to update ticket description. |
This issue should ideally leverage the functionality in the following module examples/helpers/io.ts. Would you like to work on this? @psschwei |
Yeah, I can take this one |
psschwei
added a commit
to psschwei/bee-agent-framework
that referenced
this issue
Dec 2, 2024
Signed-off-by: Paul S. Schweigert <[email protected]> Fixes i-am-bee#148 We have found that bees perform best when: * they use fewer number of tools, and * they are provided explicit instructions/role Here we updated the getting started section of the README to incorporate those recommendations into the simple example. We update the system prompt to provide explicit instructions, and we remove the search tool as it isn't needed for weather-related queries. It also adds some tips related to these two points to the appropriate section. Additionally, it adds a yarn helper method to run the simple example: `yarn run quickstart`
8 tasks
psschwei
added a commit
to psschwei/bee-agent-framework
that referenced
this issue
Dec 2, 2024
Signed-off-by: Paul S. Schweigert <[email protected]> Fixes i-am-bee#148 We have found that bees perform best when: * they use fewer number of tools, and * they are provided explicit instructions/role Here we updated the getting started section of the README to incorporate those recommendations into the simple example. We update the system prompt to provide explicit instructions, and we remove the search tool as it isn't needed for weather-related queries. It also adds some tips related to these two points to the appropriate section. Additionally, it adds a yarn helper method to run the simple example: `yarn run quickstart`
psschwei
added a commit
to psschwei/bee-agent-framework
that referenced
this issue
Dec 2, 2024
Signed-off-by: Paul S. Schweigert <[email protected]> Fixes i-am-bee#148 We have found that bees perform best when: * they use fewer number of tools, and * they are provided explicit instructions/role Here we updated the getting started section of the README to incorporate those recommendations into the simple example. We update the system prompt to provide explicit instructions, and we remove the search tool as it isn't needed for weather-related queries. It also adds some tips related to these two points to the appropriate section. Additionally, it adds a yarn helper method to run the simple example: `yarn run quickstart` Signed-off-by: Paul S. Schweigert <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
The current CLI experience gives the impression that Bee works OTTB. While it does for simple tasks, for more complex use cases we learned that narrow bees with additional instructions on only the min required tools works best.
Describe the solution you'd like
Improve CLI experience to suggest specifying a role and tools to be used.
Describe alternatives you've considered
Open to alternatives. We could consider exposing additional optional settings for user to define.
Additional context
Would be good to align more closely to UI experience. UI is changing "instructions" to "role" FYI.
The text was updated successfully, but these errors were encountered: