-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Document changes for Micro-Agents and some formatting changes #6155
base: main
Are you sure you want to change the base?
Conversation
@@ -0,0 +1,11 @@ | |||
# Micro-Agents Overview |
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.
@rbren I tried to follow your comment from the other PR and wrote this in the overview. Not sure what else to add. In its current state is it providing any value?
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.
I'm leaning towards removing this right now unless you have ideas on how to add more value here.
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.
Yeah there is a bunch of stuff we can put here about the YAML header options. Especially the way triggers
work right now
I've also been trying to standardize on Microagent
as the way this is stylized
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.
I need to get back to this PR later. I think this Micro-Agents section needs a lot of love :D
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.
Rejigged it.
Just a small detail: we talk about Repository Agents in two sections, first documenting them, then the contributing section. Then at the end of contributing, we say repo microagents should stay in their own repo 😅. Suggestions:
|
I'll reorder the Repository to be first. Can you elaborate on the first bit. Where does it mention the Repository Agents in the contributing section? Can you point me to it please so I can remove it. |
Oh, I didn't hallucinate it 😅, it was in their readme, sorry |
@@ -1,31 +1,21 @@ | |||
# Public Micro-Agents |
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.
I tried to keep the format consistent between both Micro-Agents:
- Overview
- Creating the Micro-Agent
- Best Practices
- Steps
- Example
I've tried to consolidate all the docs we have in these documentation. Including the README. My suggestion is if this is approved, we just link the README to the docs as to avoid redundancy and having to update documentation in two places. If you are good with that, I can go ahead with this as well. |
|
||
## Micro-Agent Format | ||
|
||
All micro-agents use markdown files with YAML frontmatter that have special instructions to help OpenHands accomplish |
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.
Can we standardize on microagent
(no hyphen)?
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.
Yes
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.
Done!
Co-authored-by: Robert Brennan <[email protected]>
Co-authored-by: Robert Brennan <[email protected]>
Sorry, I read on the run, but did we give up |
I swear I read somewhere that those are not fully implemented yet...However, if they are, probably need someone to explain them to me so they can be added. |
End-user friendly description of the problem this fixes or functionality that this introduces
Give a summary of what the PR does, explaining any non-trivial design decisions
Link of any specific issues this addresses
To run this PR locally, use the following command: