Multi-Repo support for Automations

Feature request for product/service

Cursor Web

Describe the request

A lot of companies (mine included) are unable to use a monorepo for absolutely everything.

In the cases where we have to split something out, there always ends up being some common issues. Types not matching between languages can be resolved with clever architecture, but some issues like feature drift can’t.

As engineers, it’s super annoying to need to remember a bunch of potential things that could go wrong with a release or to go through a giant checklist.

Automations seem like a perfect solution for this kind of issue. Unfortunately, there’s currently no way to pull in repos other than the workspace repo.

Could we please get multi-repo support for automations? I don’t really care about the workspace setup part, that can be managed by the primary repo. What I really care about is the ability to pull in a sidecar repo for reference.

Workaround

You can use the GitHub MCP as a really hacky workaround, but it’s quite painful due to rate limits.

1 Like