Hey y'all - I'm migrating my Agno security focused...
# proj-agent
r
Hey y'all - I'm migrating my Agno security focused code review agent/mcp server into an OpenHands agent using the software-agent-sdk and the first bump in the road is structured output. I'm considering using this migration attempt as a "proving ground" and developing some potential upstream candidates for software-agent-sdk structured output using my tested patterns and pydantic models. I'm looking for anyone who's also working on structured output on the SDK to chat briefly or lend their experience, and/or input from maintainers on preferences and long-term shape this feature should fit. Thoughts?
🎉 1
c
This was just asked on github too, you may want to see https://github.com/OpenHands/software-agent-sdk/issues/2566
r
@calm-artist-7206 Thank you, yes I saw that - watching it. I don't want to speak out of turn until I get my hands dirty and see how this looks in practice. Will know later this afternoon.
🙏 1
Okay. My agent is primarily a diff reviewer, not a general agent. I'm introducing a protocol boundary so the review pipeline doesn't care what's behind it, swapping Agno for LiteLLM behind that boundary, and building a structured output module that handles getting reliable JSON from any LLM provider. That module is the piece I'll propose, if approved, via PR into the OpenHands SDK, since it's one of the most-requested features. Grippy is the proving ground. The hardest part is prompt composition. Agno formats system messages in a specific way that affects review quality. I'll be capturing golden-file snapshots of the current prompts before I change anything, then verifying the new path matches. The rest is mechanical (I hope). Will report back when I have notes.
🙌 1