-
Notifications
You must be signed in to change notification settings - Fork 44.5k
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
Automatic prompting #2896
Automatic prompting #2896
Conversation
This vastly improves formatting success rate.
linting fail |
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.
add a note to news for this
And fix the linting |
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.
also you mayyyyy have infinite tests so take a look at that
CI Tests should be fixed in #2904 |
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.
This is definitely going to be good for UX. :)
Would be great to see some tests and prompt tweaks on the system prompt here. It's not perfect yet, as you can see in the example it includes steps that don't play to the strengths of an LLM. |
Signed-off-by: Merwane Hamadi <[email protected]>
Why are the unit tests getting canceled? |
Signed-off-by: Merwane Hamadi <[email protected]>
Feature/create smoke test
Enable support for loading multiple plugins per zip file
Plugins: debug line always printed in plugin load
Signed-off-by: Merwane Hamadi <[email protected]>
Signed-off-by: Merwane Hamadi <[email protected]>
…tests add decorator to tests so it's skipped if api key required but not present in the environment
@richbeales in tests/utils.py theres a new decorator to require an API key to exist before running the test that uses it. Can you add it to the tests as required here? You can see it used in https://github.com/Significant-Gravitas/Auto-GPT/blob/master/tests/integration/goal_oriented/test_write_file.py |
7bd4a0d
This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request. |
Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly. |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #2896 +/- ##
==========================================
+ Coverage 45.09% 46.08% +0.99%
==========================================
Files 60 60
Lines 2856 2890 +34
Branches 472 476 +4
==========================================
+ Hits 1288 1332 +44
+ Misses 1463 1448 -15
- Partials 105 110 +5
... and 1 file with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
Background
Prompt engineering, although in English, is a bad user experience that takes skill and practice.
This addition removes the need for laborious prompt engineering from Auto-GPT, by creating a system so easy that anybody can use it effectively.
Instead of having to manually enter the ai_config information, the user can simply now type something as simple as "Make pong", and a suitable ai_config will be automatically generated.
Changes
Documentation
Docstrings and comments throughout
Test Plan
I have implemented unit tests to cover the new and existing functions in the setup.py file.
The prompt system prompt will likely need to be further improved going forward so that it leans on AutoGPT's skill-set.
PR Quality Checklist