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

Micro-agent: Support task rejection #1482

Closed
li-boxuan opened this issue May 1, 2024 · 2 comments · Fixed by #1615
Closed

Micro-agent: Support task rejection #1482

li-boxuan opened this issue May 1, 2024 · 2 comments · Fixed by #1615
Assignees
Labels
agent quality Problems with specific agents enhancement New feature or request severity:low Minor issues, affecting single user

Comments

@li-boxuan
Copy link
Collaborator

li-boxuan commented May 1, 2024

Micro-agents, as a whole, don’t work well end-to-end yet. For example, I can barely make ManagerAgent, the one that does the task distribution, to complete the simple task used by the integration test:

poetry run python ./opendevin/main.py -i 10 -t "Write a shell script 'hello.sh' that prints 'hello'." -c "ManagerAgent"

To achieve that I think we need to do more prompt engineering, and potentially introduce more actions. I propose that we add an escalation action, because I find micro-agents often get stuck when they are assigned a task that they are not capable of.

For example, when the CoderAgent is assigned a task that is not concrete enough, it should escalate and the ManagerAgent should create a task for StudyRepoForTaskAgent first to study what files to modify, what the repo structure is, etc.

@li-boxuan li-boxuan added enhancement New feature or request agent quality Problems with specific agents labels May 1, 2024
@li-boxuan li-boxuan self-assigned this May 1, 2024
@rbren rbren added the severity:low Minor issues, affecting single user label May 2, 2024
@rbren rbren changed the title Micro-agent: Support task escalation/rejection Micro-agent: Support task rejection May 2, 2024
@rbren
Copy link
Collaborator

rbren commented May 2, 2024

This is a great idea! I'm changing it to rejection because I think letting a smaller agent call a bigger one would lead to weird loops 😄

@li-boxuan
Copy link
Collaborator Author

Yeah when I said "escalation", I was thinking of something more like "rejection" ;)

@li-boxuan li-boxuan linked a pull request May 7, 2024 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agent quality Problems with specific agents enhancement New feature or request severity:low Minor issues, affecting single user
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants