https://docs.all-hands.dev/ logo
Join Slack
Powered by
Could we name the cloud resolver/agent always “ope...
# openhands-cloud
c
Could we name the cloud resolver/agent always “openhands-ai”, as, I think, it shows up in comments? I think here the first post in this issue is by the cloud resolver, but it’s named ‘openhands-agent’. This is confusing, because the Open Source resolver is run with 
@openhands-agent
, tagged in a github comment. So how about we keep “openhands”/“openhands-ai” for the Cloud one, and “openhands-agent” only for the Open Source one? If my assumption that this first post was by the Cloud resolver is incorrect, please do correct me. https://github.com/All-Hands-AI/OpenHands/issues/9077
❤️ 1
Occasionally, some of us tag the Open Source resolver without realizing that it works differently than the Cloud resolver and without intending it in the first place. We will probably never have a good solution to that, but at least we could keep the same names for the same thing, and not the same name for different things. Idk, it might help. https://github.com/All-Hands-AI/OpenHands/pull/9574#issuecomment-3045429134
r
p
it's a CI (pipeline) agent, so why not call it openhands-ci-agent
l
I like the idea of openhands-ci-agent or maybe just openhands-ci
Or openhands-action could be good as well
c
I'm confused 😅 The cloud resolver seems to post under the name "openhands-ai" sometimes, "openhands-agent" other times, and it's called by the user with the tag "@ OpenHands". Can we settle on one of these? I don't know that we need to rename the Open Source resolver, that one posts under the name "openhands-agent", and it's called with the tag "@ openhands-agent", at least this is consistent?
Actually I'm guessing an underlying issue is the hardcoded 
git config
that we do somewhere at runtime initialization, we set the agent name and email, and that ends up applying for both. Maybe we could fix that somehow, like, not do it, and let the agent do it, maybe with a microagent telling it to? 🤔
r
My vote counts less, but I like the idea of tagging with @ OpenHands or OpenHands-Agent, in that order. -CI isn't quite right because there are non-CI use cases. -AI just seems redundant. -Action terminology works for GitHub but not things like Azure DevOps (which I'm still finalizing).
💯 1
p
-action also doesn't work for GitLab. GitLab has "Jobs" assistant feels more narrow than agent I would bias OpenHands Cloud to be summoned by @nutritious-balloon-65098 how about a -ce (community edition) kind of suffix? or -oss-ci: to make it blatantly clear this is fully open source and has no corporate boundary, should anyone want to mess setting it up on their Azure/GitLab/GitHub CI/CD pipelines?
c
I seem to recall that the OpenHands GitHub account is not available, so I think “openhands-ai” was chosen for the Cloud for that reason… (please correct me if wrong) If so, we may not be able to fix the Cloud name fully, it’s sometimes “OpenHands” sometimes “openhands-ai”.
Open in Slack
PreviousNext
Powered by