I've had a bunch of chats with OSS users and many ...
# proj-agent-canvas
e
I've had a bunch of chats with OSS users and many folks don't realize we offer a setup.sh file. I think there's an opportunity for us to make this more prominent in the onboarding of a new repo, or when the workspace is being setup. CC @breezy-kilobyte-39430
p
interesting, I actually avoided that and microagents was biased towards "the learning model should be smart enough to not need this", and "good enough defaults" one way to make it more visible could be to run a default .openhands/setup.sh so we get visual feedback in the UI somewhere that stuff is happening (initially a no-op to be customized?) https://docs.all-hands.dev/usage/prompting/repository#setup-script the other idea to me is a no-no https://docs.all-hands.dev/usage/prompting/repository#pre-commit-script because I already have other mechanisms setup exactly for this, that openhands should pick up by default (npm scripts, husky, or https://pre-commit.com/ already installed). No need for OpenHands to reinvent wheels 🙂 ideally, folks should default to devcontainers where this stuff is already setup
👍 1
e
one way to make it more visible could be to run a default .openhands/setup.sh so we get visual feedback in the UI somewhere that stuff is happening (initially a no-op to be customized?)
Yep! This is actually coming soon. We got some feedback from a customer recently. https://github.com/All-Hands-AI/OpenHands/pull/9427 In general, the feedback or user behavior I've observed is users manually instructing OpenHands on how to setup their environment before realizing that this feature exists .... so it might just be surfacing this up as an option somewhere in the UI so folks know it's there if they want it. For example, I noticed that Codex has a dedicated UI page for configuring your setup.sh. Not sure we need that, but it helps with discoverability of the feature.