Describe the request
Hi Cursor team,
I love the Parallel Agents and automatic git worktrees — they’re incredibly useful for safe, isolated agent runs. However, my team works in a common setup that isn’t fully supported yet: We have a local parent folder (not itself a Git repo) that contains many independent microservice repositories (e.g. ~/projects/services/ios-app/, ~/projects/services/backend/, ~/projects/services/search/, etc).
We open that parent folder in Cursor as our workspace.
When a single feature or task spans multiple services, we need to make coordinated changes across several repos.
The missing piece:
Cursor’s worktrees currently require a single Git repository at the workspace root. There’s no built-in way for an agent (or Parallel Agents) to automatically create and unify the same workspace/branch name (e.g. feat/update-2026) across all the relevant child repos in one run. Tools like Etz (etz.dev) solve this beautifully by scanning a parent folder of repos and creating coordinated worktrees with consistent naming under a shared workspace directory. Something similar integrated into Cursor would be perfect. What this would enable:
Tell one agent: “Implement feature X that touches ios-app, backend, and search”
- Cursor automatically creates matching worktrees/branches across those repos
- Agents can work safely in parallel without manual setup or naming drift
- Much better support for real-world microservices architectures
This is a fairly common pattern (there are already several forum threads about multi-repo / multi-root workspace limitations with agents and worktrees). Would love to see native or extensible support for this — whether it’s built-in multi-repo worktree orchestration, better integration hooks for tools like Etz, or improved multi-root workspace handling for Parallel Agents. Happy to provide more details on our folder structure or test any experimental builds!
Thanks for building an amazing product team!