Hey @ekrw, thanks for the report and the recording.
The Workspace row can get stuck on “Loading Repositories…” when there are no cloud repositories to list yet. That isn’t intended, and it’s not something you misconfigured. We’re tracking it, and I’ve let the team know. I’ll post here when there’s an update.
Projects run on Cloud Agents, so the Workspace picker only lists repositories from a connected Git provider like GitHub, GitLab, or Bitbucket Cloud, not folders on your machine. For your local clones, open the folder and start a New Chat in the Agents Window instead.
If your repos are on Bitbucket Cloud (Data Center isn’t supported for Cloud Agents), you can use them in a Project:
That makes sense about Projects running on Cloud Agents.
I was hoping that it’d be able to work with a 100% local setup by setting up a local coordinator agent, but I understand if that’s tricky.
I was interested in Projects for feature work, as right now I’ve been coordinating long-horizon feature work with poteto-mode locally by explicitly prompting a coordinator/worker-like set up in 1 chat by pointing it to a spec.
Are there any plans for supporting a 100% local setup?
A fully local Project isn’t available today. Projects run on Cloud Agents, so the coordinator lives in the cloud. It can start an agent on your computer when a step needs to run there, but that still sits inside a cloud Project with a connected repository.
Currently, the approach you described is the right one: one local chat that coordinates the work against a spec, including the poteto-mode skill you’re already using.