https://docs.all-hands.dev/ logo
Join Slack
Powered by
Are people not using the resolver much anymore or ...
# slackbot-chatter
a
Are people not using the resolver much anymore or did the setup change? This use to have lots of examples of how the agents work with stuff in slack.
🐾 1
c
I think we moved to #C0BLWB8PQ3B, with the new OSS-VM-backed resolver
Though I don't think that's a good example. It's better IMHO to look up things as they are in a thread, rather than on that channel - or any isolated-ish channel
I mean, I completely agree that what we can do with agents should be in the open - and it should, ideally, be in the thread where there was a problem
I'm sure there are some examples all throughout the channels and conversations
a
yea, there are good examples in the past. it was just a nice lens to show off how people interact with agents in slack.
c
Maybe try to find messages from this 
@oss-openhands
, and in fact, can also try on 
@smolpaws
, you can find some relevant I'm sure
I'm just saying, if we want people to see what it can do, I believe one of the best ways is to use it in-thread to solve their problem
👍 1
b
Found a few in-thread examples 🐾 Mostly oss-openhands, with one small cat contribution: • Unblocking a contributor’s PR: the contributor couldn’t edit the linked issue. oss-openhands moved the reproduction evidence and fixed its headings; the contributor confirmed they could mark the PR ready. #16913 later merged. • Docker + Traefik setup: after the workaround was explained, oss-openhands checked the source/docs gap and opened docs PR #681. Merged. • Child results not reaching the parent: oss-openhands traced TaskTool versus Canvas child behavior across both repos and filed docs issue #925. The user confirmed the SDK route worked; the docs issue remains open. • Hooks not firing in Docker: the thread found the working-folder mismatch. I turned the clarification into docs PR #941, now merged. I’d start with the first: short exchange, concrete action, and the contributor’s confirmation.
🙏 1
Open in Slack
PreviousNext
Powered by