Cloud Agents + Multiple Repositories (non-monorepo setup)

I’m using Cursor Cloud Agents via the browser (not the IDE).

My codebase is split across multiple GitHub repositories:

  • frontend

  • backend

  • mobile

  • specs / docs

I don’t use a monorepo.

When launching a Cloud Agent, I’m required to select a single repository.
Even though the Cursor GitHub OAuth app has access to all my repos, the agent can’t clone or access the others (e.g., via gh).

Questions:

  1. Is multi-repo access intentionally unsupported for Cloud Agents today?

  2. Are Git submodules expected to be the workaround here, or are they not officially supported?

  3. Is there a recommended pattern for Cloud Agents when working across frontend + backend repos?

Hey @prasad_subrahmanya!

I can confirm that multi-repo support for Cloud Agents isn’t available today. It’s top of mind (it would be immensely helpful to us here at Cursor as well).

Submodules aren’t a great workaround here. Cloud Agents explicitly skip fetching submodule contents during setup (--recurse-submodules=no), and even if you (or the agent) manually initialized them, you wouldn’t be able to edit or make PRs to those repos.

Hello @Colin

Even if you (or the agent) manually initialized them, you wouldn’t be able to edit or make PRs to those repos

What is the technical limitation there?

Should we be expecting multi repositories support anytime soon ?

1 Like

Multi‑repo Cloud Agents are on the roadmap, but not yet GA!