Skip to content
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

Added constraints and evaluations #1874

Closed
wants to merge 2 commits into from
Closed

Added constraints and evaluations #1874

wants to merge 2 commits into from

Conversation

javableu
Copy link
Contributor

@javableu javableu commented Apr 16, 2023

We can maybe improve the return message of the AI. To do this, we could give a list of straightforward instructions that can be passed to GPT-4. The text generated by a "stupid" AI will be of lower quality than the one generated by a "smart" AI. However, even a "stupid" AI can potentially produce results that match those of a "smart" AI. It certainly just needs more iteration, focus, and a list of simple instructions that he has to follow. It's important to have the AI think before he writes anything to autogpt ( critique-plan process of a single sentence).

1 Choose a sentence to work on.
2 Compose an impactful sentence.
3 Critique the sentence for clarity, coherence, grammar, and overall effectiveness. 4 Create a plan for revising the sentence, considering the critique. 5 Evaluate the plan to ensure it addresses the issues identified in the critique. 6 Refine the plan as needed.
7 Rephrase the sentence according to the refined plan. 8 Repeat steps 2-7 for additional sentences.
9 Merge the revised sentences.
10 Showcase the integrated text

For the performance evaluation, the AI has a tendency to be a bit adhd, Added refocusing criteria might help.

Background

Changes

Documentation

Test Plan

PR Quality Checklist

  • My pull request is atomic and focuses on a single change.
  • I have thoroughly tested my changes with multiple different prompts.
  • I have considered potential risks and mitigations for my changes.
  • I have documented my changes clearly and comprehensively.
  • I have not snuck in any "extra" small tweaks changes

We can maybe improve the return message of the AI. To do this, we could give a list of straightforward instructions that can be passed to GPT-4.
The text generated by a "stupid" AI will be of lower quality than the one generated by a "smart" AI. However, even a "stupid" AI can potentially produce results that match those of a "smart" AI. It certainly just needs more iteration, focus, and a list of simple instructions that he has to follow. It's important to have the AI think before he writes anything to autogpt ( critique-plan process of a single sentence).

1 Choose a sentence to work on.
2 Compose an impactful sentence.
3 Critique the sentence for clarity, coherence, grammar, and overall effectiveness.
4 Create a plan for revising the sentence, considering the critique.
5 Evaluate the plan to ensure it addresses the issues identified in the critique.
6 Refine the plan as needed.
7 Rephrase the sentence according to the refined plan.
8 Repeat steps 2-7 for additional sentences.
9 Merge the revised sentences.
10 Showcase the integrated text

For the performance evaluation, the AI has a tendency to be a bit adhd, Added refocusing critaria might help.
nponeccop
nponeccop previously approved these changes Apr 16, 2023
@nponeccop nponeccop added Needs Benchmark This change is hard to test and requires a benchmark B7 labels Apr 16, 2023
@javableu
Copy link
Contributor Author

Since it impacts the main agent's behavior, it is really hard to understand the full implications of this update. It would be nice to have user feedback on this update to see if people have noticed an improvement

@nponeccop
Copy link
Contributor

Yes, the label "Needs benchmark" is exactly for that

@nponeccop nponeccop mentioned this pull request Apr 17, 2023
1 task
@github-actions github-actions bot added the conflicts Automatically applied to PRs with merge conflicts label Apr 19, 2023
@github-actions
Copy link
Contributor

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

@p-i-
Copy link
Contributor

p-i- commented May 5, 2023

This is a mass message from the AutoGPT core team.
Our apologies for the ongoing delay in processing PRs.
This is because we are re-architecting the AutoGPT core!

For more details (and for infor on joining our Discord), please refer to:
https://github.com/Significant-Gravitas/Auto-GPT/wiki/Architecting

@waynehamadi
Copy link
Contributor

waynehamadi commented May 5, 2023

@javableu we're currently building challenges and I would like to discuss with you.

Please join use on Discord through this link https://discord.gg/autogpt (if not already)

DM me on the Auto-GPT discord channel (my discord is merwanehamadi).

@Boostrix
Copy link
Contributor

Boostrix commented May 6, 2023

Since it impacts the main agent's behavior, it is really hard to understand the full implications of this update. It would be nice to have user feedback on this update to see if people have noticed an improvement

given that these PRs are such a common thing but due to the lack of testing data also so controversial, how about coming up with support for "prompt profiles", as in a shared folder with sub-folders that contain profiles for different prompts, so that people can tinker with different profiles without stepping on anyone's toes ?

Having this sort of infrastructure in place would also provide a good baseline for regression testing and benchmarking.
It would not directly be the solution proposed in #3858, but probably would be the only solution to have our cake and eat it, while also growing test data:

This was referenced May 6, 2023
@anonhostpi
Copy link

Constraints awareness issue - #3466

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conflicts Automatically applied to PRs with merge conflicts Needs Benchmark This change is hard to test and requires a benchmark
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants