hey yall, while testing out openhands I ran into a...
# proj-agent-canvas
v
hey yall, while testing out openhands I ran into an interesting issue where an old plugin I tried to set up was blocking every message to openhands altogether. I tried to use the agent in Slack and kept getting a generic "oh no!" response, so I followed the trail checking out other issues and noticed a common theme among them being the catch all. Initially, I realized I also had critic enabled, but even with it disabled I still was getting an error. I gave my agent the DOM using ego-browser and was able to debug this. I cooked up a lil documentation to help me track the agents progress, and I linked relevant issues and things users have tried like @calm-artist-7206 as well as my proposed solution, which is to make the catch-all message agent digestible via frontmatter, following Engel's logic to maintain OpenHands with OpenHands github.com/OpenHands/enterprise/issues/745
note: the solution I'm proposing only applies to Slack it doesn't apply to the other enterprise tools yet, that would need a few more lines, let me know if I should alternatively move this to another channel!
c
Just a couple of thoughts • in OpenHands v1, we have designed the Slack connector as an Automation, fully rewritten. I haven’t personally used it with enterprise backend, but off-hand I think it should work; it has structured output • I seem to recall we have or should have somewhere a bug report on loading plugins, they shouldn’t break the conversation if unavailable
I mean, a nice behavior there is to surface a warning that the plugin couldn’t be loaded, and continue
@bland-bear-604 check if there’s an open issue on agent-sdk on plugins or skills in error -> should still start conversation; if not, post one
🐾 1
b
Checked — no existing issue. Posted: #5718
v
I've got a draft for agent-sdk here - #5716
❤️ 1
thanks on a stick 1