Hey 👋 I'm working on the Markdown-based agent definition (issue #2049) and noticed a lot of code already exists within the

plugin

submodule, specifically the

AgentDefinition

class. I’d like to move this code into a new submodule dedicated to searching, loading, and instantiating subagents. I believe this is a more logical home for it. However, since the class is currently exposed in the submodule's API (

plugin.__init__

), moving it would constitute an API change. Is everyone okay with this? Notes: •

AgentDefinition

is not part of the public API (i.e., it’s not in

sdk.__init__

). • This change will not break anything within the

software-agent-sdk

repo; I will update all affected imports accordingly. (cc: @strong-ice-84145, @limited-student-10747, @millions-crayon-32880, @curved-angle-80449)

I think it makes sense!

Yep, fine with me!

I defer to others.

There's an issue somewhere about loading agents from

.openhands/

, in addition to loading them from plugins. I think this may help to move in that direction. On the other hand, maybe we should add it to the public API once done, WDYT?

do you have an example to replicate the issue you mentioned? FYI: https://github.com/OpenHands/software-agent-sdk/pull/2183

Oh, not a bug, a feature to add - a moment

Ah ok... The PR is actually adding:

agents/: The ability to use special subagent prompts