https://docs.all-hands.dev/ logo
Join Slack
Powered by
Hey <@U0A9U2H9CFQ> and <@U070UP4FW3F>, <@U080DD1FR...
# proj-agent-canvas
l
Hey @ancient-car-4311 and @elegant-branch-54423, @wide-doctor-37830 is just finishing up a plugin for setting up your repo with OpenHands, it should be merged momentarily: https://github.com/OpenHands/extensions/pull/117 This allows you to ask OpenHands to set up your repo so it works well with OpenHands. I think that we should consider getting this into (1) our getting started docs (I’ll cross-post in #C08CR9XRQ3W) and the GUI onboarding. @ancient-car-4311 I think you mentioned you might want to get designs for an onboarding flow. Would it be OK to pass this off to you for scheduling?
w
Right now the main entry point is the 
/onboarding:setup-openhands
skill, which does a few things: 1. Helps set up or improve an AGENTS.md file, 2. Follows the repo customization steps here 3. Sets up the PR review workflow As we add more workflows and integrations we can add new skills to the plugin and reference them in the 
/onboarding:setup-openhands
skill.
e
Calvin, this is interesting! I think it's worth elevating as it's own page on the dos. Maybe under the Onboarding Openhands section, so we can guide users to use the Skill. Have you tried this on a fresh repo that hasn't used OpenHands before? Does it successfully setup these things (agents.md, PR review, repo customization)? That might be nice to include in the docs (if there's a way to make a short video of it)
With the new GUI slash command menu, the 
/onboarding
skill should just appear once this is merged. We may also want to elevate this in other ways in the GUI, like when you select a repo that doesn't have an AGENTS.md or something, and suggest this as a starting point. I don't have GUI designs for that, but could be a follow-on enhancement. Would be open to some thoughts there. CC @hundreds-twilight-32833 since this is related to first-time repo experience w/ OH.
h
Does this add 
/onboarding
?
w
It should add 
/onboarding
, but it doesn't currently appear to. I'm not sure we've got plugins loaded automatically from the extension repo, just bare skills.
Definitely worth a callout in the docs! I've run it a few times (local references, not using the slash menu) on repos that have no infra and repos that have some, and the workflow is decently robust. I.e., if there's already an AGENTS.md file it goes through the rest of the setup process then goes back and suggests improvements.
l
OK Calvin, could you add it to the onboarding section?
👍 1
Thanks!
Ideally we could just say “in the web interface or CLI, say “/setup-openhands on {org_name}/{repo_name}” or something
w
I'll add the documentation as soon as I can get the skills showing up, our plugin loading currently appears to be amiss https://github.com/OpenHands/software-agent-sdk/issues/2757
👍 1
a
Is it possible to validate that the automatically created Agents file actually helps solve tasks? Previous research has show automatically generated agents.md files to be counterproductive - https://arxiv.org/pdf/2602.11988v1
w
Some of our benchmarks are definitely amenable to an AGENTS.md ablation. Evaluating the entire onboarding pipeline is definitely something we're interested in, too. Maybe we should start a thread in #C06R25BT5B2 about that paper, I still think there's some nuance to the experiments: codebase overviews don't appear to be helpful, but agents do tend to follow instructions there and do more testing/exploration. Outside of the steps vs. success-% comparison better instruction-following and more exploration seem like a good thing. I've also tried to design the 
setup-agents-md
skill with this work in mind -- avoid big codebase overviews, surface build/test tools and quality expectations, keep it simple so a human can easily flesh it out.
a
ok, let me start a thread there - between that paper and skillsbench, there is a bit of rightful concern about just autogenerated skills/agent.md files
2 Views
Open in Slack
PreviousNext
Powered by