Do folks miss having an "open a repository" option...
# proj-agent-canvas
e
Do folks miss having an "open a repository" option when working in Local? I know you can just clone a repo locally and open it that way, but I also think it would be nice to still have a "Open repository" option that used your connected Git providers and maybe cloned the repo into the
~/.openhands/agent-canvas/workspaces
dir
c
Not sure about the main question, up to others and their workflows, just would like to note on a tiny detail: I would not love the agent (or an app) which clones random repos in random locations on my disk πŸ˜…
βž• 1
I guess I’m under the illusion that I know where things are… except python environments. I never know where those are hiding.
e
Very good point - a good reason maybe not to offer this πŸ™‚
w
I do miss it. When I want to start working with a new repo I have to tell the agent "clone X" then start a new conversation once it's cloned I have a "project parent directory" set up, so hypothetically the agent knows where to clone stuff
e
Will create an issue to get some feedback. @nutritious-balloon-65098 Please create an Enhancement issue in OpenHands/agent-canvas for adding an 'Open a Repository' feature when a user is working in a Local backend mode. This should be smart enough to know if the user has configured a GitHub, GitLab, AzureDevOps, or Bitbucket MCP server so it knows how to fetch repos.
n
I'm on it! Joe Pelletier can track my progress here.
Summary I created a GitHub Enhancement issue in the OpenHands/agent-canvas repository based on the community discussion you shared. βœ… What was done β€’ Created issue #976 β€” "Enhancement: Add 'Open a Repository' option for Local backend mode" πŸ“‹ Issue covers β€’ Background β€” captures the community feedback verbatim, including both the user pain point ("have to tell the agent to clone, then start a new conversation") and the valid counter-concern about not wanting repos cloned in random locations β€’ Detection logic β€” proposes inspecting configured MCP servers to surface only the providers the user has actually set up (GitHub, GitLab, Azure DevOps, Bitbucket) β€’ Clone location β€” recommends
~/.openhands/agent-canvas/workspaces/<provider>/<owner>/<repo>/
for a predictable, opt-in, managed location β€’ UI flow β€” provider picker β†’ repo search/filter β†’ clone if needed β†’ open conversation β€’ Open questions β€” shallow clones, pull-on-reopen, workspace parent re-use, etc. β€’ Acceptance criteria β€” checkbox list ready for implementation planning No code changes were made β€” this was purely an issue creation task.