Assigning an issue directly to @Cursor still launches the agent against a single repo (resolved from your default repo or an inline repo=owner/repo). That path doesn’t attach a multi-repo environment yet, so it’s the one piece of the original request that isn’t wired up.
Triggering from a Linear event via a Cursor Automation does support multi-repo today:
- Dashboard → Automations → New automation
- Add a Linear trigger (e.g. Issue created or Status changed)
- Select your multi-repo environment
- Save and enable
Agents started that way boot with every repo in the environment cloned and can open a PR in each repo they change (one run, one PR per repo). More detail: Automations docs and the changelog.
So multi-repo work from Linear is doable now through an Automation - the direct “assign to @Cursor” routing is the remaining gap, and it’s on our radar. This was also walked through in this thread if it’s useful.